[whatwg] Remove addCueRange/removeCueRanges

Philip Jägenstedt philipj at opera.com
Fri Aug 14 04:03:24 PDT 2009

On Fri, 14 Aug 2009 10:42:50 +0200, Dr. Markus Walther <walther at svox.com>  

> Silvia,
>> 2009/8/13 Dr. Markus Walther <walther at svox.com>:
>>> please note that with cue ranges removed, the last HTML 5 method to
>>> perform audio subinterval selection is gone.
>> Not quite. You can always use the video.currentTime property in a
>> javascript to directly jump to a time offset in a video. And in your
>> javascript you can check this property until it arrives at your
>> determined end time. So, there is a way to do this even now.
> How can polling approach that somehow monitors currentTime meet any
> halfway-decent accuracy requirements? E.g. to be accurate to 1-3 samples
> at 22050 Hz sampling frequency? I doubt your approach could fulfill this.
> To my mind, the current turn of events suggests simply to allow
> start/end attributes back into the WHATWG spec, eased by the fact that
> there were already browser implementations of it.

Highly accurate looping or fragment selection is something that requires a  
lot of work on the implementation side. I don't have a particular aversion  
to .start/.end, but think it would be wise to wait for implementor  
experience before (re)introducing any of start/end,  
addCueRange/removeCueRanges or a timed text API. Whatever the spec says  
before that is likely to be wrong.

Philip Jägenstedt
Opera Software

More information about the whatwg mailing list