13637 2011-08-03 20:38:50 +0000 <track> Cue rendering+behavior spec text should generic, not webvtt-derived 2012-04-20 02:55:44 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED FIXED a11y, a11ytf, media, WGDecision P2 normal --- 1 franko ian adrianba cooper eoconnor ian lrosenth mark_vickers mike pcotton philipj public-html-admin public-html-wg-issue-tracking rubys public-html-bugzilla oldest_to_newest 52240 0 franko 2011-08-03 20:38:50 +0000 http://www.w3.org/TR/html5/rendering.html#webvtt-cue-text-rendering-rules The spec contains several (normative) references to webvtt when defining cue and track handling. These sections should be rewritten to be generic; webvtt is one of many caption formats that could be used in html5. 53822 1 mike 2011-08-04 05:17:42 +0000 mass-move component to LC1 57038 2 cooper 2011-09-20 15:31:57 +0000 Bug triage sub-team thinks this is an HTML A11Y TF priority for the media sub-team. 60844 3 ian 2011-12-02 20:51:11 +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: no spec change Rationale: WebVTT is the format HTML is designed for (and vice versa), so mentioning it is eminently sensible. 60861 4 adrianba 2011-12-02 23:27:48 +0000 It's perfectly legitimate to have a HTML5 implementation that does not support WebVTT but does support another format. IE10 PP4 supports both WebVTT and TTML and an implementation only supporting TTML would be interoperable. Additionally, WebVTT might be used and it's not being used in HTML5 and that would be perfectly acceptable. It's unnecessary to tie these two formats together. 60897 5 pcotton 2011-12-03 19:05:59 +0000 (In reply to comment #4) > It's perfectly legitimate to have a HTML5 implementation that does not support > WebVTT but does support another format. IE10 PP4 supports both WebVTT and TTML > and an implementation only supporting TTML would be interoperable. > Additionally, WebVTT might be used and it's not being used in HTML5 and that > would be perfectly acceptable. It's unnecessary to tie these two formats > together. Can you please "suggest title and text for the tracker issue"? /paulc 60922 6 adrianba 2011-12-05 03:03:28 +0000 Raised as ISSUE-188: https://www.w3.org/html/wg/tracker/issues/188 65835 7 rubys 2012-03-20 15:16:24 +0000 WG Decision: http://lists.w3.org/Archives/Public/public-html/2012Mar/0557.html Change Proposal: http://www.w3.org/wiki/ISSUE188/GenericTextTrack 66879 8 rubys 2012-04-20 02:55:44 +0000 http://html5.org/tools/web-apps-tracker?from=7059&to=7060