16849 2012-04-25 03:26:55 +0000 <track> Nested Chapter tracks should be defined for all file types than just WebVTT 2014-04-08 01:00:42 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED INVALID a11y P2 normal --- 1 silviapfeiffer1 silviapfeiffer1 hans.hillen mike philipj public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 67003 0 silviapfeiffer1 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. 70163 1 contributor 2012-07-18 07:02:23 +0000 This bug was cloned to create bug 17846 as part of operation convergence. 73890 2 robin 2012-09-14 11:06:02 +0000 Silvia: assigning to you since you're the original reporter and this was marked INVALID. 103521 3 silviapfeiffer1 2014-04-08 01:00:42 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: none Rationale: Ian's statement on bug 17846 that other formats aren't currently interested in this is accurate. Let's wait for a use case.