W3C home > Mailing lists > Public > public-html-media@w3.org > August 2012

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 21 Aug 2012 08:31:00 +0000
To: public-html-media@w3.org
Message-ID: <bug-18634-5436@http.www.w3.org/Bugs/Public/>

           Summary: Removing SourceBuffers in "Detaching from a media
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
        AssignedTo: adrianba@microsoft.com
        ReportedBy: philipj@opera.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org


"Remove all the SourceBuffer objects from sourceBuffers and fire a
removesourcebuffer event for each one."

1. What is the point of firing one removesourcebuffer event per removed
SourceBuffer at the SourceBufferList?

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.

If there is a good answer for point 1, then point 2 could be addressed by
specifying it to the equivalent of "while (sourceBuffers.length > 0)
removeSourceBuffer(sourceBuffers[0])" or some such. In any event, it should be
specified if the SourceBuffers are removed in increasing or decreasing order,
since the difference in event order is script-visible.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 21 August 2012 08:31:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:25 UTC