- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 Aug 2012 08:31:00 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18634 Summary: Removing SourceBuffers in "Detaching from a media element" 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#mediasource-detach "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 the QA contact for the bug.
Received on Tuesday, 21 August 2012 08:31:05 UTC