This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The TextTrackCue definition in [1] has removed the 'text' attribute and the getCueAsHTML() method that were present in the previous Dec 17, 2012 CR [2]. This makes it impossible for script to access the contents of TextTrackCues. This could be fixed in one of two ways: 1) revert [1] back to [2], 2) pull the DataCue introduced in HTML 5.1 [3] into [1]. [1] http://www.w3.org/TR/html5/embedded-content-0.html#texttrackcue [2] http://www.w3.org/TR/2012/CR-html5-20121217/embedded-content-0.html#texttrackcue [3] http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#text-tracks-exposing-in-band-metadata
Cox prefers the second option: adding DataCue to HTML5 CR.
All TextTrackCue instances will now always use some more specific child interface, so you can still access the 'text' attribute where it exists. Adding DataCue doesn't seem related, since most cues won't be DataCues...
(In reply to Philip Jägenstedt from comment #2) > All TextTrackCue instances will now always use some more specific child > interface, so you can still access the 'text' attribute where it exists. > > Adding DataCue doesn't seem related, since most cues won't be DataCues... DataCues are specified for in-band metadata TextTracks[5]. [5] http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#text-tracks-exposing-in-band-metadata
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: Accepted Change: Backported DataCue to HTML 5.0 Rationale: The current CR http://htmlwg.org/heartbeat/CR-html5-20140130/ has a DataCue with a constructor at http://htmlwg.org/heartbeat/CR-html5-20140130/embedded-content-0.html#datacue .
(In reply to Silvia Pfeiffer from comment #4) > 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: Accepted > Change: Backported DataCue to HTML 5.0 > > Rationale: > > The current CR http://htmlwg.org/heartbeat/CR-html5-20140130/ has a DataCue > with a constructor at > http://htmlwg.org/heartbeat/CR-html5-20140130/embedded-content-0. > html#datacue . What does it mean to refer to a WHATWG version as "the current CR"?
(In reply to Glenn Adams from comment #5) > (In reply to Silvia Pfeiffer from comment #4) > > > The current CR http://htmlwg.org/heartbeat/CR-html5-20140130/ has a DataCue > > with a constructor at > > http://htmlwg.org/heartbeat/CR-html5-20140130/embedded-content-0. > > html#datacue . > > What does it mean to refer to a WHATWG version as "the current CR"? I think you misread. It says HTMLWG.org and it's the current CR candidate of the W3C HTML WG.
(In reply to Silvia Pfeiffer from comment #6) > (In reply to Glenn Adams from comment #5) > > (In reply to Silvia Pfeiffer from comment #4) > > > > > The current CR http://htmlwg.org/heartbeat/CR-html5-20140130/ has a DataCue > > > with a constructor at > > > http://htmlwg.org/heartbeat/CR-html5-20140130/embedded-content-0. > > > html#datacue . > > > > What does it mean to refer to a WHATWG version as "the current CR"? > > I think you misread. It says HTMLWG.org and it's the current CR candidate of > the W3C HTML WG. Ah, thanks. Though I have to wonder what publishing a CR on a non-W3C site means. Perhaps it is just an ED of a CR being staged for publishing on TR?
(In reply to Glenn Adams from comment #7) > (In reply to Silvia Pfeiffer from comment #6) > > > > I think you misread. It says HTMLWG.org and it's the current CR candidate of > > the W3C HTML WG. > > Ah, thanks. Though I have to wonder what publishing a CR on a non-W3C site > means. Perhaps it is just an ED of a CR being staged for publishing on TR? It's a CR *candidate* and it has been announced on the html-admin list. It will eventually replace the current CR on TR.