- From: Kornel Lesiński <kornel@geekhood.net>
- Date: Wed, 31 Dec 2008 16:39:06 +0000
On 31.12.2008, at 15:15, Maciej Stachowiak wrote: > It does make sense I guess, that certain fields should not be > subject to automatic spellchecking. However, three counterpoints: > > 1) At least Safari's spellchecking won't mark a word misspelled > until you hit a space; fields that contain data which would be > flagged by the spellchecker but which are also likely to contain > internal whitespace are rare. In Webkit spellchecking is also done when field loses focus, so even a single-word fields would be flagged. > 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. > 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. I don't like current proposal either, because "true"/"false" value is inconsistent with other boolean attributes in HTML. IMHO it should be nospellcheck="nospellcheck" (which also solves problem of forcing spellchecking where it doesn't make sense). -- regards, Kornel
Received on Wednesday, 31 December 2008 08:39:06 UTC