[whatwg] Exposing spelling/grammar suggestions in contentEditable

Benjamin Hawkes-Lewis bhawkeslewis at googlemail.com
Sat Dec 11 06:11:55 PST 2010

On Fri, Dec 3, 2010 at 10:05 AM, Adrian Sutton <adrian.sutton at ephox.com> wrote:
> Notably, users do not want the full browser context menu with some custom
> additions (though obviously this would make a good option for some users) -
> having "View Source" for example is quite damaging to the usability of rich
> text editors since it would display a read-only source without running the
> editors source filtering, as opposed to the editor's built in source view
> which filters correctly and is editable.

If "View Source" is verifiably damaging to the usability of rich text
editors then isn't it damaging to the usability of "contenteditable"
everywhere, and shouldn't it be fixed at the UA level rather than left
to individual websites to work around?

Safari and Chrome do not show the "View Source" option when you click
on "contenteditable" (or other text content).

Safari does not show "Inspect Element" either unless you enable the
"Developer" menu.

Benjamin Hawkes-Lewis

More information about the whatwg mailing list