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

[Bug 7871] there's more meaning to a password field than just being obstructed. it's really only for passwords / credentials. firefox stores them in the password manager, for example, meaning FF really gives it the meaning "password", not just "obstructed". the defi

From: <bugzilla@wiggum.w3.org>
Date: Tue, 20 Oct 2009 23:55:05 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1N0OXh-0001GN-0O@wiggum.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2009-10-20 23:55:04 ---
I disagree; there are use cases for which type=password makes sense, that are
not credentials. For example, a game where the user has to type in a guess or
bid, where it is plausible that other players will be near the user at the

Password managers are just using heuristics to learn the likely values of
forms. There's not really any difference between that and the form prefilling
that browsers  do in other contexts, e.g. on this bug editor page.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 20 October 2009 23:55:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:41 UTC