- From: <bugzilla@jessica.w3.org>
- Date: Thu, 14 Oct 2010 10:00:10 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11011 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #9 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-14 10:00:10 UTC --- Browsers aren't going to gate their implementation of next-gen JS features until the next JS spec is done, any more than they are going to gate their implementation of HTML features until HTML is done. :-) So I think the solution here is for us to at least try to see if browser vendors can implement this in their RegExp implementations before we add new attributes here. From a holistic point of view, it seems like the objectively better long-term solution. 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: see above -- 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 Thursday, 14 October 2010 10:00:12 UTC