Re: [whatwg] Assigning media resources represented as DOM objects to a media element

On Sat, Feb 16, 2013 at 3:46 AM, Glenn Maynard <glenn@zewt.org> wrote:

> a) This isn't the case.  The tricky bit was defining precisely when
> autorevocation happens; this has been resolved (the "global script clean-up
> jobs list").  There's a remaining piece (
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17765), but while it'll
> take some thought to do that in a clean way (so it can be applied to
> different APIs concisely), there's nothing magic there.
>

Serves me right for checking the latest published version instead of the
real spec... Sorry.

It may be that "there's nothing magic there", but in comment #17 Ian seems
less than enthusiastic ("this is nuts, IMHO").

Even if you get past that, you still have the problem that revoked URLs are
useless. It's impossible to do something equivalent to video2.src =
video1.src (which works today). Also, getting access to the underlying
source object is a valuable feature, especially for MediaStream and
MediaSource objects which have interesting APIs on them.

Rob
-- 
Wrfhf pnyyrq gurz gbtrgure naq fnvq, “Lbh xabj gung gur ehyref bs gur
Tragvyrf ybeq vg bire gurz, naq gurve uvtu bssvpvnyf rkrepvfr nhgubevgl
bire gurz. Abg fb jvgu lbh. Vafgrnq, jubrire jnagf gb orpbzr terng nzbat
lbh zhfg or lbhe freinag, naq jubrire jnagf gb or svefg zhfg or lbhe fynir
— whfg nf gur Fba bs Zna qvq abg pbzr gb or freirq, ohg gb freir, naq gb
tvir uvf yvsr nf n enafbz sbe znal.” [Znggurj 20:25-28]

Received on Friday, 15 February 2013 20:10:39 UTC