This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In a discussion with David Baron, we are having trouble figuring out exactly what sort of interface our DOM nodes created from WebVTT markup are supposed to implement -- In short, it's not clear what sort of elements we are supposed to be creating in section 4.4 -- HTMLElement with local name "b" or HTMLBoldElement (for example"). Some clarification of this would be helpful.
HTMLBoldElement doesn't exist. All the elements listed are defined to use HTMLElement in the HTML spec. So the WebVTT spec is correct.
I'm sure the spec may well be "correct", what we're saying is that it's not necessarily "clear", this could be improved upon.
Section 4.4 is very clear on this: http://dev.w3.org/html5/webvtt/#webvtt-cue-text-dom-construction-rules It talks about HTMLElement and lists the localNames of the nodes. I don't know what's unclear about that.
If it were clear, there wouldn't be confusion -- but there is, and this has been asked about by people this week during discussions about the track element / WebVTT. All we're hoping for is some clearer wording. The local-name vs node-type confusion in particular seems to have struck certain people as ambiguous.
(In reply to comment #1) > HTMLBoldElement doesn't exist. All the elements listed are defined to use > HTMLElement in the HTML spec. So the WebVTT spec is correct. Oops, turns out I was wrong. <span> is HTMLSpanElement. The rest use HTMLElement. Maybe the spec should say [[ An HTML span element. ]] with "span" being a link to http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-span-element instead of the current [[ HTMLElement element node with localName "span". ]]
https://github.com/w3c/webvtt/pull/223
*** Bug 28469 has been marked as a duplicate of this bug. ***