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

[whatwg] Exposing spelling/grammar suggestions in contentEditable

From: Ashley Sheridan <ash@ashleysheridan.co.uk>
Date: Sun, 28 Nov 2010 10:32:43 +0000
Message-ID: <1290940363.9024.6.camel@localhost.localdomain>
On Sun, 2010-11-28 at 11:27 +0200, timeless wrote:

> On Sat, Nov 27, 2010 at 10:19 PM, Charles Pritchard <chuck at jumis.com> wrote:
> > Is there room for discussion of an API
> there's room to discuss such things.
> > to expose misspelled ranges of text in contentEditable?
> I'm worried about privacy risks.
> Some devices have a tendency to learn passwords as typed words, other
> private terms get added to known words. If a web page has the ability
> to talk to the spell checker, it could send it a stream of things
> which aren't in a standard dictionary to determine if they are in the
> user's custom dictionary.

But why would a password field ever be tied to a contentEditable
section? As far as I was aware, password fields are very special, and
don't do a lot of things that other fields do, so it wouldn't be
difficult for it to not do something else would it?!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20101128/f5519147/attachment.htm>
Received on Sunday, 28 November 2010 02:32:43 UTC

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