[Bug 24576] Calling URL.createObjectURL() on a closed Blob

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

--- Comment #10 from Anne <annevk@annevk.nl> ---
I see why you ended up with the synchronous closed check now.

Man, allowing a blob to be closed really makes things harder. Basically
anything that takes a blob needs to account for this somehow. 

In case of FormData it would be its rather complicated serialization
algorithm... Which might end up doing this for several blobs in a row and then
one of those could be closed, but we cannot start throwing at that point. Which
would mean we would need some kind of lock upfront to prevent them from being
closed as we want to read them in a bit and not throw. How much has this been
thought through? Am I missing something obvious?


As for your scenario, you are saying that if you have a blob URL before the
blob is closed, you can read it? The read operation algorithm does not seem to
support that.

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

Received on Monday, 17 March 2014 18:20:22 UTC