W3C home > Mailing lists > Public > public-html@w3.org > January 2009

Re: autocomplete on form

From: Ben Boyle <benjamins.boyle@gmail.com>
Date: Sun, 18 Jan 2009 11:11:55 +1000
Message-ID: <5f37426b0901171711yffa420ar8fa1408288e5e748@mail.gmail.com>
To: "Jonas Sicking" <jonas@sicking.cc>
Cc: "Lachlan Hunt" <lachlan.hunt@lachy.id.au>, "Ian Hickson" <ian@hixie.ch>, "HTML WG" <public-html@w3.org>

I have used form@autocomplete="off" recently too.

It's on a credit card screen, which is only accessed after verifying a
bill or other type of payment... not the kind of page that would be
uncovered by crawling or casual browsing (and the reason I cannot
provide a direct URL). I reckon this would not be uncommon for
'autocomplete' making detecting its usage in the wild problematic.

For what it's worth, I chose form@autocomplete over input@autocomplete
because of a personal preference to limit the number of (HTML4)
validation errors returned.

There is an additional, albeit small, authoring benefit: if I add
another control to that form, it will inherit the autocomplete
behaviour. I don't have to remember to specify autocomplete. I don't
have to worry if the application developers add another field (and
they may not even know this HTML nuance). And I don't have to worry if
the application developers use a framework to add a control, such
frameworks likely not implementing autocomplete. It is easier to
manage a single form element than the set of form control elements.

The above only holds true in our scenario because we do wish for
autocomplete to be disabled for every field within this particular

Received on Sunday, 18 January 2009 01:12:31 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:41 UTC