RE: TextTrackCue changes

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?

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 19:57:32 UTC