- From: <bugzilla@jessica.w3.org>
- Date: Wed, 05 Jun 2013 04:24:14 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21851 --- Comment #21 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> --- I've thought about this some more and my suggestion for resolution is at http://www.w3.org/html/wg/wiki/User:Spfeiffe/TextTrackChange#.283.29_Removal_of_TextTrackCue_constructor On top of renaming TextTrackCue to AbstractTextTrackCue and introducing an unparsed TextTrackCue API, I also suggest renaming inBandMetadataTrackDispatchType on TextTrack to cueFormatHint. The cueFormatHint would be filled by the browser not just for in-band tracks, but also for files coming from <track>. For example, parsing a WebVTT file with captions would result in a cueFormatHint of "webvtt", but parsing a WebVTT file with metadata or chapters or descriptions would give a cueFormatHint of "plaintext". Or if the browser knew that it was metadata and knew it was JSON, it could set cueFormatHint to "json". Then, it's clear which XXXCue object should be used to parse the .cues in the TextTrack. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 5 June 2013 04:24:20 UTC