[whatwg] Exposing spelling/grammar suggestions in contentEditable
adrian.sutton at ephox.com
Sun Nov 28 08:27:30 PST 2010
On 28 Nov 2010, at 15:52, Benjamin Hawkes-Lewis wrote:
> On Sun, Nov 28, 2010 at 3:41 PM, Adrian Sutton <adrian.sutton at ephox.com> wrote:
>> User's expect a rich text editor
>> to override the browser default context menu to provide things like
>> properties for images, lists, tables etc and the other stuff usually found
>> in a rich text editor's context menu. However, once that is done, the
>> browser's built-in spelling suggestions are no longer available, effectively
>> losing support for inline spell checking.
> "The user agent may also provide access to its default context menu,
> if any, with the context menu shown. For example, it could merge the
> menu items from the two menus together, or provide the page's context
> menu as a submenu of the default menu."
It could, but it doesn't. Any browser that tried doing that would likely just run into compatibility complaints and have to revert it.
More importantly, there's no way to instruct or even suggest that the browser should which leaves users without functioning spell checking and rich text authors with no way to meet the demands of users.
Adrian Sutton, CTO
UK: +44 1 628 353 032 US: +1 (650) 292 9659 x717
Ephox Blogs http://people.ephox.com/, Personal Blog http://www.symphonious.net/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg