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

[whatwg] Remove addCueRange/removeCueRanges

From: Dr. Markus Walther <walther@svox.com>
Date: Fri, 14 Aug 2009 11:54:07 +0200
Message-ID: <4A85343F.2060207@svox.com>

Silvia Pfeiffer wrote:
> 2009/8/14 Dr. Markus Walther <walther at svox.com>:
>> Hi,
>>> The .start/.end properties were dropped in favor of media fragments,
>>> which the Media Fragments Working Group is producing a spec for.
>> Who decided this? Has this decision been made public on this list?
>>> It will
>>> be something like http://www.example.com/movie.mov#t=12.33,21.16
>> var audioObject = new Audio();
>> audioObject.src
>> ='data:audio/x-wav;base64,UklGRiIAAABXQVZFZm10IBAAAAABAAEAIlYAAESsAAACABAAZGF0Yf7///8AAAAA....';
>> // play entire audio
>> audioObject.play();
>> // play (0.54328,0.72636) media fragment
>> ?????
> Not in this way. In fact, the new way will be much much simpler and
> does not require javascript. 

With the code snippet given I was pointing out that it is not obvious
(to me at least) how the proposed media fragment solution covers data
URIs. If it is not meant to cover them, it is limited in a way that the
solution it seeks to replace is not.

> Or if you really wanted to do it in javascript, you'd only need to
> reload the resource:

Of course we want to do this dynamically in JavaScript - IMHO it would
be the norm not the exeception to select fragments based on user input.
Precomputed fragments are of limited use. I don't quite understand why
the dynamic case is so often underrepresented in these discussions...

-- Markus
Received on Friday, 14 August 2009 02:54:07 UTC

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