W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2012

[Bug 18634] Removing SourceBuffers in "Detaching from a media element"

From: <bugzilla@jessica.w3.org>
Date: Mon, 01 Oct 2012 21:24:38 +0000
Message-Id: <E1TInTi-0001HU-T0@jessica.w3.org>
To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18634

--- Comment #2 from Aaron Colwell <acolwell@chromium.org> 2012-10-01 21:24:38 UTC ---
(In reply to comment #1)
> (In reply to comment #0)

> > 
> > 2. When is activeSourceBuffers updated, if at all? Depending on when it is
> > updated the order of events would be different, which is script-visible and
> > should therefore be part of a test suite for the API.
> 
> It gets updated when tracks from different SourceBuffers get enabled/selected.
> I attempt to cover this in section 3.3.5, but I can see right now that I've
> been a little sloppy here and don't mention when the events fire.
> 
I just realized that you were talking about what happens on the detach
algorithm specifically. Here are the new steps for the detach algorithm which I
believe cover your concerns.

1. Set the readyState attribute to "closed".
2. Set the duration attribute to NaN.
3. Remove all the SourceBuffer objects from activeSourceBuffers.
4. queue a task to fire a simple event named removesourcebuffer at
activeSourceBuffers.
5. Remove all the SourceBuffer objects from sourceBuffers.
6. queue a task to fire a simple event named removesourcebuffer at
sourceBuffers.
7. queue a task to fire a simple event named sourceclose at the MediaSource.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 1 October 2012 21:24:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 1 October 2012 21:24:40 GMT