- From: <bugzilla@jessica.w3.org>
- Date: Wed, 08 Jul 2015 22:57:02 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27980 --- Comment #5 from Matt Wolenetz <wolenetz@google.com> --- I agree that going back to a synchronous model is too big a hammer for this problem. I spoke with Aaron Colwell and two complementary ideas resulted: 1) Remove any text and logic in abort() spec and "abort" event spec involving aborting a Remove() (or aborting a range removal operation). Abort is really meant to reset the parser state. Remove() (or range-removal triggered by reducing duration) is already not allowed while processing appended media. 2) Disallow (and issue an exception) any reduction of duration that would remove buffered media. Remove() is available as a mechanism to explicitly remove buffered media, and once completed, a web app can inspect the buffered attribute prior to doing any explicit duration reduction operation. I'm not sure how widespread is any usage of abort() to stop an in-progress Remove() (or duration-change-triggered range removal), though I doubt there are any interoperable expectations around HTMLMediaElement state for such a scenario. The more concerning breaking change is #2: web apps would then be receiving exceptions for a duration change scenario that is more realistically used today than the scenario changed by #1. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 8 July 2015 22:57:06 UTC