[whatwg] Remove addCueRange/removeCueRanges

[Dr. Markus Walther]

Hi,

please note that with cue ranges removed, the last HTML 5 method to
perform audio subinterval selection is gone.

AFAIK, when dropping support for 'start' and 'end' attributes it was
noted on this list that cue ranges would provide a replacement to
dynamically select, say, a 3-second range from a 1-hour audio source.

So, if cue ranges will indeed be dropped, could browser vendors and
standards people consider putting 'start' and 'end' back in, just like
Safari had it for a while (albeit buggy)?

Actually, out of curiousity: could gapless concatenation of several
audio objects be added as well, e.g.

audioObject1.append(audioObject2)

or even

audioObject.join([audioObject1,audioObject2,...,audioObjectN)

Just my 2c.

--Markus

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.
>