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.
The major use case here remains being able to provide both spell checking as you type and a customised context menu within rich text editors. Today that is not possible on any browser that I know of and it's one of if not the biggest selling point for our non-JavaScript editor (we offer both Java applet and Javascript based editors). This use case would require providing spelling suggestions, not just identifying the location of spelling errors. 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? Regards, Adrian Sutton. ______________________ Adrian Sutton, CTO UK: +44 1 628 353 032 Ephox http://www.ephox.com/ Ephox Blogs http://people.ephox.com/, Personal Blog http://www.symphonious.net/
