<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.2">
</HEAD>
<BODY>
On Mon, 2010-11-29 at 10:40 -0800, Charles Pritchard wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
> Date: Sun, 28 Nov 2010 15:54:04 +0100
> From: Christoph P?per<<A HREF="mailto:christoph.paeper@crissov.de">christoph.paeper@crissov.de</A>>
> To: whatwg group<<A HREF="mailto:whatwg@lists.whatwg.org">whatwg@lists.whatwg.org</A>>
> Subject: Re: [whatwg] Exposing spelling/grammar suggestions in
> contentEditable
> Message-ID:<<A HREF="mailto:62959690-0E26-4BBC-AB4F-F9726F24CAF9@crissov.de">62959690-0E26-4BBC-AB4F-F9726F24CAF9@crissov.de</A>>
> 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:<<A HREF="http://lists.w3.org/Archives/Public/www-style/2010Oct/0849.html">http://lists.w3.org/Archives/Public/www-style/2010Oct/0849.html</A>
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.
</PRE>
</BLOCKQUOTE>
<BR>
<BR>
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?<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
Thanks,<BR>
Ash<BR>
<A HREF="http://www.ashleysheridan.co.uk">http://www.ashleysheridan.co.uk</A><BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>