W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2009

[whatwg] Remove addCueRange/removeCueRanges

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 14 Aug 2009 10:26:50 +1000
Message-ID: <2c0e02830908131726h4b00c2f8wcd2599e7d8a7e1f7@mail.gmail.com>
On Fri, Aug 14, 2009 at 3:31 AM, David Singer<singer at apple.com> wrote:
> At 10:31 ?+0200 13/08/09, Philip J?genstedt wrote:
>> Hi,
>> We would like to request that addCueRange/removeCueRanges be dropped from
>> the spec before going into Last Call. We are not satisfied with it and want
>> to see it replaced with a solution that includes (scriptless) timed text
>> (a.k.a captions/subtitles). I don't think that this will be finished in time
>> for Last Call however, because we need implementor experience to write a
>> good spec. However, we have no intention of implementing both cue ranges and
>> its replacement, so it is better if the spec doesn't provide any solution
>> for now.
>> I have been briefly in contact with other browser vendors and while I
>> cannot speak for them here, I hope those that agree will chime in if
>> necessary.
> We reluctantly agree. ?We suggested a re-think a year ago, and though that
> got some support, it didn't get the editor's support. ?We do not have an
> implementation of the current spec., and don't expect to.
> <http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-July/015284.html>
> We do think the functionality is important, and are saddened to agree with
> this proposal, however.

I am actually hoping that we could attach callbacks to time-aligned
text segments which makes the whole approach to cue ranges more
generic. Hopefully I will have a demo of this within the next few
weeks, so we can discuss further.

Received on Thursday, 13 August 2009 17:26:50 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:15 UTC