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

> The UAs are capable (and should) do it themselves if they want to offer spell-check across boundaries.

Ok, meaning that there is no specification that defines when they are and when they are not. So after Safari, IE, Chrome, Firefox each implement this differently and will have different rules as to what constitutes a word and what doesn't. So in order to either turn word recognition on or off, there will be tons of little hacks, probably changing from browser version to browser version to achieve just that. That's not a good idea.

> I think it's a very bad idea to bake into the spec a limitation such as this one.

I don't think it's "baked in". All it does is to use a more generic replaceText event for text replaced through spellchecking. Should a later version of the spec use a more specific spellChecker event that can handle more complex setups, it should not in any way break anything.

> Therefore the event target must not be a text node, but rather a Range.

Actually that's already happening. The current targetRange for replaceText is specified as:

```
Set the value of targetRange to a new range that covers the text that is to be replaced.
```



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