- From: Glenn Adams <glenn@skynav.com>
- Date: Thu, 26 Sep 2013 14:14:23 -0700
- To: "Jerry Smith (WINDOWS)" <jdsmith@microsoft.com>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, public-html <public-html@w3.org>
- Message-ID: <CACQ=j+fpBQy3e0cyhkYk9iNabb46xuJVUx+nGDZKCRNcfbYmEQ@mail.gmail.com>
On Thu, Sep 26, 2013 at 2:11 PM, Glenn Adams <glenn@skynav.com> wrote: > > > On Thu, Sep 26, 2013 at 12:57 PM, Jerry Smith (WINDOWS) < > jdsmith@microsoft.com> wrote: > >> I see two comments opposed to restoring the text attribute and the >> constructor to the base texttrackcue object. I am in favor of that, and >> thought others were as well. How was this specific topic resolved and >> committed? Was there a broader consensus for this change? >> > > Silvia can provide further feedback; however, it you take a look at [1], > you can see that the IDL definition of TextTrackCue has been made > identical to the definition in [2]. That resolved the fork between the two > specs regarding this interface definition. > > In addition, a new DataCue interface was defined at [3], containing both a > binary and a text data accessor, which meets the needs of exposing in-band > @kind metadata tracks. This satisfies the known use cases for exposing such > content (as far as I'm aware). > > Finally, the text attribute was just restored to VTTCue today in [4], > which restores the raw text getter/setter for VTT cue instances. > > Overall, I'm satisfied with these changes and feel it is the right way to > proceed. > I should add that I had a lengthy face to face discussion with the Google Media folks on the Blink team yesterday, and they also agreed with this approach. Indeed, I expect that these changes will be made in short order in Blink now that the spec fork has been resolved. > > [1] > http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#texttrackcue > [2] > http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#texttrackcue > [3] > http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#datacue > [4] > https://dvcs.w3.org/hg/text-tracks/raw-file/default/webvtt/webvtt.html#vttcue-interface > > >> >> Jerry >> >> -----Original Message----- >> From: Silvia Pfeiffer [mailto:silviapfeiffer1@gmail.com] >> Sent: Wednesday, September 25, 2013 7:52 PM >> To: public-html >> Subject: TextTrackCue changes >> >> Hi all, >> >> In conclusion of the recent discussion on this mailing list, I have made >> the following changes: >> >> 1. Removed the WHATWG fork: >> TextTrackCue is now fully abstract again. See >> https://github.com/w3c/html/commit/580e7e6f98fbd82586aa7e894efbe8c16b99701f >> This resolved https://www.w3.org/Bugs/Public/show_bug.cgi?id=22903 . >> >> 2. Introduced DataCue and clarify kind=metadata: >> DataCue has been introduced to deal with in-band metadata tracks. >> Clarified that all non-rendered tracks are of kind "metadata". >> >> See >> >> https://github.com/w3c/html/commit/e254307b50a0411ca5e8f37587817804c3dd3d14 >> >> https://github.com/w3c/html/commit/026452845c5e83860c70b82cddba1bc9e94da7ad >> >> This resolves https://www.w3.org/Bugs/Public/show_bug.cgi?id=21851 >> >> Note that I've added a .text attribute as a convenience accessor for Web >> devs, but I'd be happy to remove it until we see a need for such a >> convenience. >> >> Also note that I have only applied the changes to the HTML5.1 >> specification. Please register a bug if you would like to see it backported. >> >> Regards, >> Silvia. >> >> >> >
Received on Thursday, 26 September 2013 21:15:14 UTC