Closed Bug 620664 Opened 10 years ago Closed 10 years ago
Add support for the <track> element to the HTML parser
The HTML5 spec now requires <track> to parse like <param> and <source>. Mike(tm) Smith has patched the Java version of the parser. Need to land the translation into m-c.
Mike, are you ok with being the hg author of record for the code that is autogenerated from your Java patch?
Attachment #499006 - Flags: review?(jgriffin) → review+
(In reply to comment #1) > Mike, are you ok with being the hg author of record for the code that is > autogenerated from your Java patch? Yes
Attachment #499005 - Flags: approval2.0? → approval2.0+
Thanks. Landed. http://hg.mozilla.org/mozilla-central/rev/912a9991c5c6 http://hg.mozilla.org/mozilla-central/rev/9497c1308688
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Don't forget "dev-doc-needed" keyword for those bugs, otherwise documentation is a game of hazard.
Adding link to specification.
Documentation updated to indicate Firefox compatibility: https://developer.mozilla.org/en/HTML/Element/track Also listed on Firefox 6 for developers.
If I understand well this bug, the documentation is not accurate. Support for <track> wasn't the goal of this bug, merely its support by the HTML parser. In other terms, the compatibility matrix in https://developer.mozilla.org/en/HTML/Element/track shouldn't have been updated (I've corrected it). And in Firefox 6 for developers, I've updated the sentence to be more accurate. (I got feedback from a web developer trying to use this feature using Aurora and the MDN information — yes! There are some people using these! — and surprised that it failed)
(In reply to comment #8) > If I understand well this bug, the documentation is not accurate. Support > for <track> wasn't the goal of this bug, merely its support by the HTML > parser. Well, this bug is in the parser component. Resummarizing to make things clearer.
Summary: Add support for the <track> element → Add support for the <track> element to the HTML parser
You need to log in before you can comment on or make changes to this bug.