[editing-explainer] behavior of text nodes inside cE=typing (#22)

I recently filed a bug in the Chromium project:
https://code.google.com/p/chromium/issues/detail?id=436107

The problem I had was that Chrome was removing a text node. This causes problem in my code because I keep references to text nodes. Having a node vanish from the document is frustrating thing to have to deal with when you are writing an editor.

I think cE=typing should specify a few behaviors for text nodes contained within it. The behaviors would be in line with the "no magic" ideas of cE=typing.

Some examples:
- don't unilaterally remove, modify, join, split text nodes
- allow empty text nodes

The bug on Chromium is marked as won't fix, and frankly I can't blame them. However, we should collect all the magical behaviors related to text nodes on all UAs that make editing very hard and spec the proper non-magical behavior in cE=typing.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing-explainer/issues/22