W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2010

[whatwg] Exposing spelling/grammar suggestions in contentEditable

From: Adrian Sutton <adrian.sutton@ephox.com>
Date: Fri, 3 Dec 2010 22:19:03 +0000
Message-ID: <BEF5E9E3-C9B7-4A49-A165-3B743035411C@ephox.com>
On 3 Dec 2010, at 22:06, Charles Pritchard wrote:
> Yes, I understand that.
> 
> Your statement relates to a defect in the current flexibility of the "context menu".
> 
> I fully understand that, you wouldn't need the context menu to be more flexible, if you had access to suggestions, as you have your own custom context menu implemented.

That's not the way I see it.  Right now I'm perfectly happy with the complete flexibility I have in the context menu. I don't want to try and tie in with the browser's context menu because that will reduce the flexibility.

> Recognizing that "suggestions" can not be shared with the DOM, the alternative is to address defects in the context menu.
> 
> It seems to me that were the context menu more easily manipulated via scripting, your use requirement (having suggestions) would be handled without exposing the suggestions to the DOM.

If I were able to script the context menu, and the context menu contains the spelling suggestions then the spelling suggestions are effectively in the DOM.

> Still, your use case does require that spelling ranges be made available.


If I use the current approach of replacing the context menu then yes.  If I'm scripting an existing context menu then no - if it's a spelling error the suggestions will already be in the context menu and I won't need to do anything special with them (but I would have to remove every *other* menu and add my own custom ones).

I really don't see why if spelling suggestions are a security/privacy concern this couldn't be an opt-in feature like local storage is. That said, I've also not been convinced of the privacy or security concerns beyond just making sure you don't run a buggy/insecure spell checker (much like you shouldn't run a buggy/insecure browser).  As has been noted, the information such as user language and OS/Browser type is pretty trivial to determine through a range of other means.

Regards,

Adrian Sutton.
______________________
Adrian Sutton, CTO
UK: +44 1 628 353 032
Ephox http://www.ephox.com/
Ephox Blogs http://people.ephox.com/, Personal Blog http://www.symphonious.net/




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20101203/8bf5edf0/attachment.htm>
Received on Friday, 3 December 2010 14:19:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:02 UTC