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

Reviewing this again, it appears to be a Safari-only problem, and Safari's spell checking for contenteditable is already broken due to attempts as cross-element spellchecking ( https://github.com/w3c/editing-explainer/issues/50 ), so I don't see why this should hold everything else up. Including a standard spell checker is what other browsers do, so this should not be magic for Safari to implement as well. Such a spell checking APi could be part of a new spec so that it does not hold up Safari's implementation of contentEditableTyping.

This seems to be the only sane solution at fixing spell checking in a relatively secure manner. 

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