It _may_ be worth discussing (as I am not all knowing) but I cannot see a way that these APIs could be added without opening up a user to privacy violations. It is somewhat irksome to me that I have raised these exact issues in the past in the context of implementing editors in canvas and you appear to have chosen to ignore me.
--Oliver On Nov 27, 2010, at 12:19 PM, Charles Pritchard wrote: > Is there room for discussion of an API to expose misspelled ranges of text in > contentEditable? > > This would be building upon the spelling and grammar checking section: > http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html#spelling-and-grammar-checking > > A method for a contentEditable section, along the lines of > getSpellcheckRanges() would allow for content editors, > to stylize and provide further UI controls around spell checking. Such an API > could be used to warn the user that > they have possibly misspelled text, in a similar way to how word processors > convey the information. > > It may not be feasible at the moment, but it could be worth some discussion. > A Range list seems appropriate, though > it would need something along the lines of getSuggestedSpelling() on each > range. > > > -Charles >
