- From: <bugzilla@jessica.w3.org>
- Date: Mon, 22 Jun 2015 12:36:34 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25353 --- Comment #22 from Bob Lund <b.lund@cablelabs.com> --- (In reply to Silvia Pfeiffer from comment #21) > I'm curious where people stand with this? DataCue was removed from the HTML5 > spec. Is there still interest in a generic cue container object? Was > anything implemented? Could we just close this bug and other DataCue related > bugs and declare it a failed approach? We're implementing a polyfill to expose DASH Events in the MPD and ISOBMFF media segments where MSE is used for the DASH client. Initially we defined a DASHEVentCue object interface. It had the same interface as DataCue. For this reason, we decided to implement DataCue instead of DASHEventCue. I think all metadata cues will be the same - what would be different? It's all about passing data to JavaScript that is opaque to the UA. If DataCue goes away then I think we'll have a proliferation of more specific metadata cues, all with the same interface. As soon as this work is completed we'll make it available for others to evaluate and use. Bob -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 22 June 2015 12:36:37 UTC