Re: [editing-explainer] How does cE=typing support IME text replacement? (#34)

We need to agree on a major point before we can move forward on this: is it okay to require sites to do special work to support a few key scenarios involving text replacement- certainly IMEs, maybe spellchecking, maybe overtype (insert key).

Sites already know that they have to do special work to support basic editing. For that reason, I believe the target audience for ce=typing should be sophisticated developers writing frameworks like ckeditor and fidus writer. Adding a requirement for special handling of spellchecking and IMEs does not seem like too much work for those folks. It makes the architecture of ce=typing much cleaner as well. So I say we require this special handling (you must convert the affected range to a single text node in order for overtype/IME/spellcheck to work).

In the end this doesn't make site developers lives harder, because they should be using frameworks anyway and this will be invisible to them.

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