- From: Ryosuke Niwa <notifications@github.com>
- Date: Wed, 27 May 2015 21:15:23 -0700
- To: w3c/editing-explainer <editing-explainer@noreply.github.com>
Received on Thursday, 28 May 2015 04:16:19 UTC
I think the basic answer will be that (in my proposal), the browser doesn't do anything specific with regards to 2 and 3. e.g. 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. Similarly, if the app decides not to insert text, then the browser doesn't do anything with the caret element or the text nodes around it. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing-explainer/issues/57#issuecomment-106165528
Received on Thursday, 28 May 2015 04:16:19 UTC