- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 Jun 2011 07:20:15 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12816 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-06-21 07:20:15 UTC --- 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'm not really convinced this is needed. While we may add some of the things in the cited e-mail, it's unlikely we'd add many of them as immutable construction-time-only features rather than just as attributes that can be changed arbitrarily. If we ever need to, we can always make the API wait until the event loop spins before doing anything, in which case we can expose any optional construction-time argument we want as object attributes, without having an open() method. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Tuesday, 21 June 2011 07:20:17 UTC