- From: Johannes Wilm <notifications@github.com>
- Date: Wed, 27 May 2015 17:57:02 -0700
- To: w3c/editing-explainer <editing-explainer@noreply.github.com>
Received on Thursday, 28 May 2015 00:57:37 UTC
I changed the title to what this is actually about. replaceText itself should already be able to handle multiple Typing Nodes. What I wonder about is whether not instead it is conceivable that the `Custom spelling dictionary` (the term Chrome uses for it) could be turned off and then the standard spelling provided through direct JavaScript calls, or whether that still constitutes a security concern. For any more complex editor, havign direct access to a spell checker seems to be the only way to go. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing-explainer/issues/50#issuecomment-106127741
Received on Thursday, 28 May 2015 00:57:37 UTC