[whatwg] Exposing spelling/grammar suggestions in contentEditable
adrian.sutton at ephox.com
Fri Dec 3 02:05:38 PST 2010
On 3 Dec 2010, at 00:16, Jonas Sicking wrote:
> As a browser implementer, I can tell you I won't implement any
> specification that isn't motivated by use cases. So I definitely think
> you want to establish use cases if you're hoping to get browsers to
> implement your suggestion.
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. There are also styling considerations which are addressed quite well with the current oncontextmenu handler and using pure HTML but which would likely become quite difficult when trying to integrate with a browser's native menu.
What further information do you require around this use case?
Adrian Sutton, CTO
UK: +44 1 628 353 032
Ephox Blogs http://people.ephox.com/, Personal Blog http://www.symphonious.net/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg