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

Yes, how about hiding the functions behind some kind of access control like that used for access to microphone and webcam?

The use case is that one will create a rich text editor with a custom GUI and custom elements in which the displayed HTML is too complex for the browser to "automagically" be able to figure out what language the text is written in or what parts of HTML are to be understood as a sentence or a paragraph and also we may want to combine the automatic part of the spell or grammar checking (and there needs to be a clear separation between the two for us on the Javascript side of things) with some custom things  -- such as domain specific dictionaries that are used in addition to the available browser spell checker. This is therefore all something we need to be able to control ourselves. Check for example the CKeditor spell checker plugin: http://docs.ckeditor.com/#!/guide/dev_spellcheck .Why do you think they don't just let the browser native spell checker run instead of this third site tool? Wouldn't that be a lot easier for them? It would, but it wouldn't be as integrated to the 
 editor a
 nd what the spell checker did would be rather out of control.

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