W3C home > Mailing lists > Public > public-html@w3.org > September 2013

Re: TextTrackCue changes

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sat, 28 Sep 2013 11:47:28 +1000
Message-ID: <CAHp8n2=tahcphC_ZRPvFFEqNV9HqfCaA+B6T5i=KJXAi_o5PeQ@mail.gmail.com>
To: Glenn Adams <glenn@skynav.com>
Cc: public-html <public-html@w3.org>
On Sat, Sep 28, 2013 at 3:30 AM, Glenn Adams <glenn@skynav.com> wrote:
> On Wed, Sep 25, 2013 at 8:52 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
> wrote:
>> 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.
> If HTML5 (as opposed to 5.1) is expected to go through another LC/CR due to
> substantive changes, then I would want these changes back-ported. However,
> I'm not sure I would want this change to be the one that causes going back
> to LC/CR. Can you comment on whether there are yet any other substantive
> changes made in HTML5 post CR1?

It is possible that we may go through another round of LC with HTML5.
There have been other features with substantial changes, too.

> If HTMLT5 is not expected to undergo another LC/CR from any other
> substantive change, then it would be useful to at least deprecate the
> TextTrackCue constructor and the text and getCueAsHTML members in HTML5 CR1
> (which doesn't entail introducing a substantive change).

I have just cherry-picked the TextTrackCue change for HTML5 CR1 - I
actually thought I had already done that to avoid the spec split.

I guess we will introduce DataCue into HTML5 CR1 once there is browser
support. Otherwise it will just go on the list of features at risk.

Received on Saturday, 28 September 2013 01:48:16 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:05 UTC