[whatwg] Exposing spelling/grammar suggestions in contentEditable
simonp at opera.com
Mon Nov 29 04:04:00 PST 2010
On Sun, 28 Nov 2010 17:27:30 +0100, Adrian Sutton
<adrian.sutton at ephox.com> wrote:
> 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
>>> in a rich text editor's context menu. However, once that is done, the
>>> browser's built-in spelling suggestions are no longer available,
>>> 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.
Note that the referenced spec section is about <menu> context menus, a
feature that to my knowledge is not implemented in browsers yet and not
used by Web content yet.
More information about the whatwg