[whatwg] Spellchecking mark III

Robert O'Callahan robert at ocallahan.org
Wed Dec 31 12:26:10 PST 2008

On Thu, Jan 1, 2009 at 4:15 AM, Maciej Stachowiak <mjs at apple.com> wrote:

> 2) The proposal Hixie linked seems way overengineered for this purpose.
> First, it allows spellchecking to be explicitly turned on, potentially
> overriding normal defaults, but that seems wrong; an <input type="email">
> should never spellcheck regardless of the page author says. I can't see any
> valid use case for the author turning spellchecking on regardless of UA
> defaults or user preferences.

It allows you to have a region of text where spellchecking is disabled via
the spellcheck attribute, but containing subregions where spellchecking is

Second, it allows spellchecking to be controlled at a finer granularity than
> editability, for which again I think there is no valid use case. Both of
> these aspects make the feature more complicated to implement and harder to
> understand, compared to just having a way to only disable spellchecking at
> the same granularity as editing.

A use case is editable program code, where spellchecking is disabled, but
where spellchecking is enabled inside comments. Maybe that sounds a little
far-fetched for today's Web applications, but some IDEs (e.g. Eclipse)
support this so it seems like something we'd want in the future.

"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090101/ceaa41e5/attachment-0001.htm>

More information about the whatwg mailing list