- From: <bugzilla@jessica.w3.org>
- Date: Tue, 25 Oct 2011 23:37:28 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14510 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ian@hixie.ch Resolution| |NEEDSINFO --- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-10-25 23:37:28 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: How the conversion is done for in-band tracks depends on the specification that defines how to map that format to the HTML API. For out-of-band tracks, the spec seems unambiguous that the literal value in the attribute or API is left unmodified. Is there something I can do in the spec to make this clearer? What led you to thinking this might not be the case? -- 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, 25 October 2011 23:37:34 UTC