- From: <bugzilla@jessica.w3.org>
- Date: Tue, 24 Aug 2010 19:43:47 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9637 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-08-24 19:43:46 --- 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. -- 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, 24 August 2010 19:43:49 UTC