- From: <bugzilla@jessica.w3.org>
- Date: Fri, 22 Feb 2013 01:19:46 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21080
Bug ID: 21080
Summary: TextTrackCue() constructor incorrectly assumes WebVTT
content type
Classification: Unclassified
Product: HTML WG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: CR HTML5 spec
Assignee: robin@w3.org
Reporter: glenn@skynav.com
QA Contact: public-html-bugzilla@w3.org
Step 4 of the description of TextTrackCue() needs to be reformulated in a
manner that is independent of the use of WebVTT.
At present, the following language appears:
"Let cue's text track cue text be the value of the text argument, and let the
rules for its interpretation be the WebVTT cue text parsing rules, the WebVTT
cue text rendering rules, and the WebVTT cue text DOM construction rules.
[WEBVTT]"
Since a text track need not make use of WebVTT, this language is overly
constraining, and presumes a specific content format for track cue data.
In order to resolve, I propose adding a (possibly optional) MIME media type
parameter to TextTrackCue() so that the caller can specify the associated
content type semantics. For example, the caller might specify text/vtt if
WebVTT semantics apply to the cue, or might specify application/xml+ttml if
TTML semantics apply, etc. Using the specified MIME type, the UA can select the
appropriate set of rules to associate with the cue.
If this parameter were made optional, then the default value might be specified
as text/vtt.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 22 February 2013 01:19:47 UTC