- From: <bugzilla@jessica.w3.org>
- Date: Mon, 20 Oct 2014 21:44:20 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27116 Bug ID: 27116 Summary: <track> element is used for more than just "explicit external timed text tracks" Product: HTML WG Version: unspecified Hardware: PC OS: other Status: NEW Severity: normal Priority: P2 Component: HTML5 spec Assignee: dave.null@w3.org Reporter: john@foliot.ca QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-admin@w3.org, public-html-wg-issue-tracking@w3.org The current spec states: "The track element allows authors to specify explicit external timed text tracks for media elements." Yet, immediately afterwards, when defining the the various @kind keywords associated to the <track> element, one of those @kinds is Chapters (i.e. <track kind="chapters" src="" label="Chapters"> - "Chapter titles, intended to be used for navigating the media resource. Displayed as an interactive (potentially nested) list in the user agent's interface.") - which is clearly not an external timed text track - and while timing may in fact be present, the rendering in the user-interface is not (as defined by the same spec) intended to display/not display content based on time-stamps, but rather to render a static view of specific time-markers, intended for use in navigation. Recommendation is to revisit the definition of the <track> element, to broaden its scope. Perhaps something like: "The track element allows authors to specify explicit external supplemental resources for media elements." -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 20 October 2014 21:44:22 UTC