25236 2014-04-02 19:50:36 +0000 autocomplete fields: password types 2014-04-14 18:03:32 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED P1 normal Unsorted 1 ian ian eoconnor gcasto ian MattN+w3 mike mkwst contributor oldest_to_newest 103291 0 ian 2014-04-02 19:50:36 +0000 It would be useful for change-of-password fields for there to be a new autofill field that indicates that the password is a new one, as in: <input type=password name=newpassword autocomplete="new-password"> <input type=password name=confpassword autocomplete="new-password"> 103319 1 mkwst 2014-04-03 09:01:34 +0000 Chrome will implement whatever syntax we agree upon here. The lack of a standard mechanism for signifying password/confirmation fields (as opposed to other fields of type 'password') is a pain point for our password autofill system. I do believe there's value in distinguishing between new and confirmation password fields, if only because it allows us another heuristic with which to distinguish between "Sign _up_" and "Sign _in_" forms. If we wanted to be super clear, of course, we could add some metadata to the form itself. 103323 2 mkwst 2014-04-03 09:31:37 +0000 Also: as you mentioned on the list, UA's handling of "Change password" forms would benefit from being able to explicitly specify that a particular field of type 'password' is your old password. 'old-password' sounds like a reasonable value. 103640 3 ian 2014-04-09 21:59:44 +0000 Can you elaborate on the new vs confirmation case? 103653 4 mkwst 2014-04-10 07:25:55 +0000 I'm not sure what I was thinking when I typed that. Both the "new password" and "confirm new password" fields could be designated via the same autocomplete value. That shouldn't create any problems. 103785 5 eoconnor 2014-04-11 22:41:59 +0000 Safari would like to have old-/current- (unsure on naming) and new-password autocomplete tokens. 103787 6 ian 2014-04-11 22:42:56 +0000 Should we not just assume that any field that is type=password and doesn't have an explicit autocomplete="" value is the current (aka old) password? 103820 7 ian 2014-04-14 17:55:51 +0000 Evan pointed out to me privately that the problem with assuming that missing fields mean "current password" is that today there's lots of pages where it doesn't mean that. But I really want to avoid having people write: <input type=password name=password autocomplete=current-password> But maybe "current-password" is not so bad... 103821 8 ian 2014-04-14 18:03:10 +0000 Ok, done. 103823 9 contributor 2014-04-14 18:03:32 +0000 Checked in as WHATWG revision r8573. Check-in comment: Add some autofill keywords for usernames and passwords. http://html5.org/tools/web-apps-tracker?from=8572&to=8573