- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Mon, 8 Jul 2013 11:55:36 +1000
- To: public-texttracks@w3.org
On Sat, Jul 6, 2013 at 12:42 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > > 7. WebVTT API for Browsers > 7.1 WebVTTCue interface > 7.2 Extension of the TextTrack interface for region support > 7.3 Extension of the TextTrackCue interface for region support > 7.4 TextTrackRegion interface > 7.5 TextTrackRegionList interface I've already noticed one bug and am fixing it: section 7.3 should not extend the TextTrackCue, but the WebVTTCue. So, I'm dropping that section. I'm also renaming WebVTTCue to VTTCue (see https://www.w3.org/Bugs/Public/show_bug.cgi?id=22020 ). Also, what do people think about the TextTrackRegion interface. Should that be restricted to WebVTT files? My original motivation for creating a generic TextTrackRegion rather than a VTTRegion was that other files (in particular CEA708 and TTML files) also have regions with similar properties. But I may be assuming too much. I'm thinking of renaming TextTrackRegion to VTTRegion and TextTrackRegionList to VTTRegionList. And we would not add the TextTrackRegionList to the TextTrack object, but create a VTTTrack object with these extended interfaces. Cheers, Silvia.
Received on Monday, 8 July 2013 01:56:24 UTC