This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
If bug 9636 is accepted, it would be better to have the "default" keyword for the default state. So, the autocomplete IDL attribute would be able to return "on", "off" and "default" instead of "on", "off" and "". Concretely, it should not change a lot of things but it would be more clear IMO to check for foo.autocomplete == "default" instead of foo.autocomplete == "" which sounds much more like a hack. In addition, we can't be sure if in the future another state wouldn't be added with no keyword.
I would expect .autocomplete to return only "on" or "off". That way script can easily know whether autocomplete is active. "default" isn't too useful, IMO.
Indeed, it would be better to have the autocomplete IDL attribute reflecting the resulting autocompletion state which can only be 'on' or 'off'.
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 spec change Rationale: I haven't added "default" as a value of the IDL attribute, because that would mean adding a new keyword to the attribute, and I really don't want to start adding new features here. The empty string represents the attribute being absent, this is a common idiom in the language. I haven't made .autocomplete represent the current state rather than the content attribute, because in general people complain when we do that (citing defaultValue on <input>), and because in general I don't think we want to make it possible for banks to detect when the user has gone out of his way to enable autocomplete even though the page has disabled it.