- From: Simon Pieters <simonp@opera.com>
- Date: Mon, 29 Nov 2010 13:04:00 +0100
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 >>> 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." >> >> http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#context-menus > > 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. -- Simon Pieters Opera Software
Received on Monday, 29 November 2010 04:04:00 UTC