- From: Johannes Wilm <notifications@github.com>
- Date: Wed, 27 May 2015 21:23:50 -0700
- To: w3c/editing-explainer <editing-explainer@noreply.github.com>
Received on Thursday, 28 May 2015 04:24:52 UTC
> if the editor is serializing the edited content as HTML, then the HTML parser will create a single text node instead of two text nodes that are adjacent to each other since HTML isn't round trip safe for such a DOM tree. True, but that's why normal HTML isn't a good enough format to store part of the DOM in when doing collaborative editing based on contenteditable=true. Instead we've had to create a script that serializes it to json so that sibling text nodes are preserved. See this open source project: https://github.com/fiduswriter/diffDOM > Similarly, regardless of whether the app decides to insert text or not, the browser doesn't do anything with the caret element or the text nodes around it. I think we need to be more specific. Else we will create problems for collaborative environments. Especially if browsers behave differently. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing-explainer/issues/57#issuecomment-106166274
Received on Thursday, 28 May 2015 04:24:52 UTC