620664 - Add support for the <track> element to the HTML parser

Status: RESOLVED FIXED

(Core :: DOM: HTML Parser, defect)

Description

[Henri Sivonen (:hsivonen)]

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.

Comment 1

[Henri Sivonen (:hsivonen)]

Attachment: Add track element support to the parser

Mike, are you ok with being the hg author of record for the code that is autogenerated from your Java patch?

Comment 2

[Henri Sivonen (:hsivonen)]

Attachment: Add tests for void elements

Comment 3

[Michael[tm] Smith [:sideshowbarker]]

(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

Comment 4

[Henri Sivonen (:hsivonen)]

Thanks. Landed.

http://hg.mozilla.org/mozilla-central/rev/912a9991c5c6
http://hg.mozilla.org/mozilla-central/rev/9497c1308688

Comment 5

[j.j.]

Don't forget "dev-doc-needed" keyword for those bugs, otherwise documentation is a game of hazard.

Comment 6

[Eric Shepherd [:sheppy]]

Adding link to specification.

Comment 7

[Eric Shepherd [:sheppy]]

Documentation updated to indicate Firefox compatibility:

https://developer.mozilla.org/en/HTML/Element/track

Also listed on Firefox 6 for developers.

Comment 8

[Jean-Yves Perrier [:teoli]]

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)

Comment 9

[Henri Sivonen (:hsivonen)]

(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.