[whatwg] Exposing spelling/grammar suggestions in
ash at ashleysheridan.co.uk
Mon Nov 29 13:53:18 PST 2010
On Mon, 2010-11-29 at 10:40 -0800, Charles Pritchard wrote:
> > Date: Sun, 28 Nov 2010 15:54:04 +0100
> > From: Christoph P?per<christoph.paeper at crissov.de>
> > To: whatwg group<whatwg at lists.whatwg.org>
> > Subject: Re: [whatwg] Exposing spelling/grammar suggestions in
> > contentEditable
> > Message-ID:<62959690-0E26-4BBC-AB4F-F9726F24CAF9 at crissov.de>
> > Content-Type: text/plain; charset=us-ascii
> > Charles Pritchard:
> >> > 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.
> > Methinks this belongs into CSS:<http://lists.w3.org/Archives/Public/www-style/2010Oct/0849.html
> Should the issue re-arise in the CSS groups: it seems that most of the
> vendors are against exposing system dictionary identified misspelled words.
> ::spelling would need to have the same level of security as a:visited --
> only foreground, background color would accept alteration. Anything
> else would expose the data being highlighted.
Erm, how would that help? It's currently very easy right now to exploit
the a:visited thing to grab an entire history list, which I presume is
what you're on about?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg