[Bug 27980] [MSE] Ambiguous behaviour when running sourcebuffer.abort()

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

Jerry Smith <jdsmith@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jdsmith@microsoft.com

--- Comment #6 from Jerry Smith <jdsmith@microsoft.com> ---
We agree that aborts of remove() and range removal algorithms don't have
deterministic outcomes, and further believe that allowing aborts for those
operations doesn't seem like a primary use case requirement.  We support
disallowing abort for these cases.

The additional proposal to require remove() to make duration changes that
remove buffered data also makes sense.  There might be some compat exposure to
existing MSE sites, I guess.  That's probably manageable.  Duration changes
that remove buffered data would require both a remove() and an explicit
duration setting change.

Note this last use case also might not be a primary one.  Playlists or ad
handling would more commonly remove everything from the buffer and start with
new content.

I recommend making both changes proposed in this bug.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 24 August 2015 21:08:06 UTC