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

> 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.

That is the current spec. or it will be. But a future version of the spec may allow this. The point here is not to allow browsers all kinds of uncontrolled and unspec'ed behavior -- on the contrary. The point is to make them behave in a predictable way.

> 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.

If it's not hard to determine what the rules are that make something be a word, then it should not be difficult to write that down in a specification. Doing this would make it something that could be included. Even then, I think we need a way to turn this off if we don't want a thousand hacks around this.

Once you have written a specification draft on the word division question, feel free to add it to a PR. If you additionally provide a way to turn this feature off, we can even merge it all into this repository before the F2F.

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