7871 2009-10-10 02:21:46 +0000 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 2016-11-10 09:10:35 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#password-state P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking rink.rf public-html-bugzilla oldest_to_newest 28216 0 contributor 2009-10-10 02:21:46 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#password-state Comment: 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 definition doesn't mentiong this meaning at all. Posted from: 78.46.195.14 28620 1 ian 2009-10-20 23:55:04 +0000 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 time. 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.