22814 2013-07-26 17:33:00 +0000 Both autocomplete="on" and autocomplete="off" are UA hints and thus should use MAY, not SHOULD language 2014-04-10 17:07:51 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED INVALID P2 normal --- 22815 1 eoconnor dave.null MattN+w3 mike mounir public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 91325 0 eoconnor 2013-07-26 17:33:00 +0000 Currently, the spec for autocomplete="off" says > When an element's autofill field name is "off", the user agent should not remember the control's value, and should not offer past values to the user. And SHOULD, in RFC 2119, basically means "MUST unless you have a really good reason." Consider a site with a user signup form and a login form. The signup form doesn't have autocomplete attributes. A user starts to fill in the registration form, and the user's browser offers to create a new, unique password for this site. The user agrees. Later on, the user browses to the site and tries to log in. The login form has autocomplete="off". Per spec, the UA should not offer to fill in the stored password for the user, because the author expects the user to type the password in themselves. But in this scenario the user doesn't even know the password in the first place. Ultimately, the autocomplete="" attribute represents a hint to UAs, but UAs should be free to do whatever is in their user's interests with the hint. 92864 1 robin 2013-09-03 12:33:26 +0000 What you describe here is IMHO very much "a really good reason" to do things differently. It seems to me that you've just made the SHOULD work really well. 103685 2 eoconnor 2014-04-10 17:07:51 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: No change. Rationale: Fair enough. I agree with Robin.