Re: [editing-explainer] replaceText input event could span multiple Typing Nodes (#50)

There are no weird surprises for developers here. The problem with CE=true are that it manipulates the DOM in whimsical ways. This is not happening here. You still have full control of the DOM. So this is a very far cry from the problems of CE=true and I don't see it as a show-stopper for either dev or user.

> LibreOffice and apparently Safari haven't figured out how to do this without losing formatting.

Well at least they allowed the spell-check to correctly fix the partially-styled word. That they didn't preserve the style exactly is secondary. My problem is you are baking in the spec an impossibility. You're making it completely impossible, per-spec, for me to even have a chance to match LibreOffice's capability using native spell-check, let alone improve on it.

I don't think it'll be nearly as hard as you imagine to make it clear to all browsers that you do not intend for two adjacent strings to be a word. But that's just my opinion. If others are genuinely worried about it we can try to spec it.


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