[Bug 18591] New: addsourcebuffer and removesourcebuffer events appear unhelpful

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18591

           Summary: addsourcebuffer and removesourcebuffer events appear
                    unhelpful
           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


http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#sourcebufferlist-events

The addsourcebuffer and removesourcebuffer events are fired when:

* addSourceBuffer: "Add the new object to sourceBuffers and fire a
addsourcebuffer on that object." (Ambiguous which the target object is, but
presumably sourceBuffers.)

* removeSourceBuffer: "If sourceBuffer is in activeSourceBuffers, then remove
it from that list and fire a removesourcebuffer event on that object." and
"Remove sourceBuffer from sourceBuffers and fire a removesourcebuffer event on
that object."

* Detaching from a media element: "Remove all the SourceBuffer objects from
sourceBuffers and fire a removesourcebuffer event for each one."

What is the use case for these events? Since the application is the only source
of added or removed buffers, telling the application about it appears very
strange.

It looks like this API may have taken inspiration from HTML's TextTrackList,
but the reason there are addtrack and removetrack events in that context is
that the application needs to be notified about in-band tracks, i.e. an
external source of events.

-- 
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 Thursday, 16 August 2012 14:02:18 UTC