W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2006

[whatwg] Spellchecking proposal #2

From: Matthew Paul Thomas <mpt@myrealbox.com>
Date: Sun, 25 Jun 2006 17:16:09 +1200
Message-ID: <1fcd1855dc93558f18c9a703e32ffc18@myrealbox.com>
On Jun 25, 2006, at 2:02 AM, Lachlan Hunt wrote:
> ...
> However, the proposed spellcheck attribute has one major advantage 
> over all of those: it's being designed to allow the user to easily 
> override it if they want to.

But realistically, browsers won't "allow the user to easily override it 
if they want to", because any interface for doing that would be absurd. 
For example, in Opera:

     |  Select all         #A |
     |  Check spelling        |
     |  Really check spelling |

Teehee. Or in Safari (where the spellchecking interface is confusing 
enough already, thanks):

     |  Find          >|________________________________
     |::Spelling::::::>|  Spelling?                  #: |
                       |  Check Spelling             #; |
                       |/ Check Spelling as You Type    |
                       |/ Spellcheck Sometimes          |
                       |__Spellcheck Always_____________|

Firefox doesn't seem to have a design for spellchecking published on 
their Web site yet. Maybe, if they're going to support a new attribute 
for authors to influence spellchecking, they'll expose it in the 
Preferences dialog:

     [/] Check my spelling in Web page forms
         [ ] Even if the page author disagrees

... Yeah, right. Bottom line, browser vendors will either ignore the 
attribute, or they'll make it configurable in a really obscure place 
(about:config or equivalent), and leave 99.9% of people wondering 
vaguely why spellchecking works on some pages and not others.

Matthew Paul Thomas
Received on Saturday, 24 June 2006 22:16:09 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:47 UTC