[Bug 16849] New: <track> Nested Chapter tracks should be defined for all file types than just WebVTT

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16849

           Summary: <track> Nested Chapter tracks should be defined for
                    all file types than just WebVTT
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: silviapfeiffer1@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 25 April 2012 03:27:02 UTC