Re: [editing-explainer] How can sites access browser spellchecking? (#36)

> Since an end user can't even tell whether a given word spans across multiple elements or not

This is for the editor to make sure -- that things that should be spell checked together do not span across elements.

> editors already need to support deletion across multiple elements when the user presses backspace

How the deletion key works can be configured to the last detail in the JavaScript. But the spell checker, when turned on, will simply add red lines and the editor has no more control over where those lines are put -- except through hacks. And sure, I cans till make it so that if the user selects that MexicoMaus shouldn't actually be changed to whatever the spell checker comes up with, it will just look wrong if it's underlined, yet the user's correction choice is not accepted.

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