This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/ Multipage: https://html.spec.whatwg.org/multipage/#text-track-model Complete: https://html.spec.whatwg.org/#text-track-model Referrer: Comment: How should WebVTT integrate with "text track cue data"? Posted from: 213.112.154.156 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.101 Safari/537.36 OPR/25.0.1614.35 (Edition beta)
https://html.spec.whatwg.org/#text-track-cue-data Working on bug 25959, it's not clear to me what words specs should use to make "text track cue data" be the specific type, text in the case of WebVTT. I can't help but think in object-oriented terms, where it's a bit odd to have an interface member of unknown type which is made known by a subinterface. I tentatively suggest dropping "text track cue data" from HTML, so that WebVTT can define its own "text track cue text" just like the other things it adds to the text track cue model. The text track cue data is only used for chapters in HTML: https://html.spec.whatwg.org/#text-track-cue-data To fix that, I'd change the "rules for rendering the cue in isolation" extension point to something more explicit like "rules for extracting the chapter title" that operates on a text track cue of a specific subtype, so that "text track cue text" is something WebVTT internal. (Point of confusion: Why is it called "rules for rendering the cue in isolation" anyway? The rules don't render anything, they return a string...)
Checked in as WHATWG revision r8859. Check-in comment: Simplify how we define how to get chapters out of WebVTT https://html5.org/tools/web-apps-tracker?from=8858&to=8859
Thanks! I'm updating the WebVTT spec in https://github.com/w3c/webvtt/pull/172