This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Feedback by the CSS WG, see http://lists.w3.org/Archives/Public/public-tt/2015Apr/0007.html The list in section 5.5 (http://dev.w3.org/html5/webvtt/#webvtt-cue-text-dom-construction-rules) doesn't match with the description of how Selectors work; in particularly, Class, Voice, and Lang objects are all "span" elements here, but are "c", "v", and "lang" elements in Selectors. Selectors is written on top of the DOM, though, so these should match. (But we hear this difference is intentional?)
Further feedback by CSS WG: You can remove the entire section about how to evaluate the selector once section 5.5 defines an accurate DOM mapping; just specify that it matches over the equivalent DOM defined in 5.5. Or are there (intentional) differences between selecting against a WebVTT DOM and the mapped HTML DOM?
Section 5.5 is only used for VTTCue.getCueAsHTML(), for the purposes of rendering there are no HTML elements involved. However, as actually implemented some equivalent DOM is created. In Blink there's VTTElement and I'm sure other engines have some kind of internal representation.
We could define a WebVTT DOM but that is strictly speaking an editorial issue, the black-box behavior should be the same. In either case, it can be implemented with DOM or with some other representation. We could add some non-normative text to the DOM construction section saying that the rules are for getCueAsHTML(), not for rendering.
(In reply to Simon Pieters from comment #3) > We could define a WebVTT DOM but that is strictly speaking an editorial > issue, the black-box behavior should be the same. In either case, it can be > implemented with DOM or with some other representation. I'd prefer we leave it as generic as possible. That way, non-browser video players might find it useful, too. > We could add some non-normative text to the DOM construction section saying > that the rules are for getCueAsHTML(), not for rendering. I'll prepare a PR for this.
https://github.com/w3c/webvtt/pull/193
https://github.com/w3c/webvtt/pull/193 is merged, is that all we need to do for this bug?