W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2010

[whatwg] Exposing spelling/grammar suggestions in contentEditable

From: Charles Pritchard <chuck@jumis.com>
Date: Sun, 28 Nov 2010 19:49:16 -0800
Message-ID: <5007C38C-2B3F-4E81-9BBA-56D627D254FB@jumis.com>
And now it's being brought up in the context of content editable.

My understanding of prior conversations were that contentEditable is a reasonable method to explore input editing.

The content within an editable area is already exposed: xhr is available. I understand that a 'custom' system dictionary could expose private data ... Just as 'suggestions' on form elements do.

What breach is enabled by using a limited spell check?

dataTransfer has done a lot to demonstrate unobtrusive ways of transferring limited data, and gives me hope that there may be more interop in the future.

On Nov 28, 2010, at 6:56 PM, Oliver Hunt <oliver at apple.com> wrote:

> 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
Received on Sunday, 28 November 2010 19:49:16 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:28 UTC