This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 16849 as part of operation convergence. Originally filed: 2012-04-25 03:26:00 +0000 Original reporter: Silvia Pfeiffer <silviapfeiffer1@gmail.com> ================================================================================ #0 Silvia Pfeiffer 2012-04-25 03:26:55 +0000 -------------------------------------------------------------------------------- The spec currently says about <track>: "Furthermore, if the element's track URL identifies a WebVTT resource, and the element's kind attribute is in the chapters state, then the WebVTT file must be both a WebVTT file using chapter title text and a WebVTT file using only nested cues." This requirement is in the HTML spec for the <track> element, but it applies only to WebVTT files. This is too exclusive. Instead, it should be extended for all files that are linked to from a <track> element with a kind=chapters. It should be reformulated into something like: "Furthermore, if the element's kind attribute is in the chapters state, then the element's track URL must identify a text track resource that is using only chapter title text and is using only nested cues." Then the definitions from WebVTT for "text track resource using chapter title text" and "text track resource using only nested cues" need to be included in the HTML spec, too. This will make it possible for browsers to handle chapters the same way no matter what resource they come from. As a consequence, the WebVTT spec would just refer to the HTML spec as being a resources format that supports these two definitions. ================================================================================
This is WebVTT-specific because it's got to do specifically with WebVTT features. If there are other formats that support this kind of thing that vendors are interested in implementing support for, then we should consider those separately.