On Mon, Apr 29, 2013 at 1:03 AM, Silvia Pfeiffer <silviapfeiffer1@gmail.com>wrote: > > > On Sat, Apr 27, 2013 at 12:03 AM, Glenn Adams <glenn@skynav.com> wrote: > >> >> On Fri, Apr 26, 2013 at 1:48 AM, Simon Pieters <simonp@opera.com> wrote: >> >>> On Fri, 26 Apr 2013 06:18:50 +0200, Glenn Adams <glenn@skynav.com> >>> wrote: >>> >>> While Cox supports the process of separating VTT specific APIs from the >>>> more generic TextTrackCue API, we oppose certain changes that introduce >>>> backward compatibilities, including: >>>> >>>> (1) the removal of the TextTrackCue constructor; >>>> >>> >>> The previous TextTrackCue constructor was actually WebVTT-specific (it >>> set all the WebVTT properties and "text" was parsed using WebVTT parsing >>> rules). >>> >> >> Thanks for that reminder. Indeed, I had posted a bug on this and >> suggested an alternative approach in [1]. >> >> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=21080 >> > > I was thinking of this solution initially, too. But let's continue to have > this discussion in the bugs and on the main mailing list. I have some > feedback that I will post to the bug. Thanks for pointing out this bug and > sorry for the delays to get to it. > See also the related bug [2]. [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=21079 I suspect a resolution for the new [revert text/getCueAsHTML] bug (21851) needs to be coordinated with the resolution of these two earlier bugs (21079 and 21080).
Received on Monday, 29 April 2013 18:21:18 UTC