PrivateCoffee/element-web
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 3

describe all reasons why we need a custom textify algorithm

Browse source
This commit is contained in:
Bruno Windels 2019-08-02 13:45:35 +02:00
parent 995ae41e67
commit ad776fbfca
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/ciderEditor.md
View file

@ -16,8 +16,10 @@ The parts are then reconciled with the DOM.
When typing in the `contenteditable` element, the `input` event fires and When typing in the `contenteditable` element, the `input` event fires and
the DOM of the editor is turned into a string. The way this is done has the DOM of the editor is turned into a string. The way this is done has
some logic to it to deal with adding newlines for block elements, ... some logic to it to deal with adding newlines for block elements, to make sure
so doesn't use `innerText`, `textContent` or anything similar. the caret offset is calculated in the same way as the content string, and the ignore
caret nodes (more on that later).
For these reasons it doesn't use `innerText`, `textContent` or anything similar.
The model addresses any content in the editor within as an offset within this string. The model addresses any content in the editor within as an offset within this string.
The caret position is thus also converted from a position in the DOM tree The caret position is thus also converted from a position in the DOM tree
to an offset in the content string. This happens in `getCaretOffsetAndText` in `dom.js`. to an offset in the content string. This happens in `getCaretOffsetAndText` in `dom.js`.