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

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

Glenn Maynard <glenn@zewt.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |glenn@zewt.org

--- Comment #23 from Glenn Maynard <glenn@zewt.org> ---
(In reply to Arun from comment #19)
> But this does mean that some methods will throw, and some won't.  I think
> FileReader.readAsxxx throwing is fine; I think close() itself throwing if
> closing an already closed Blob is fine. Any of those failing differently
> seems confusing.

Reading from a Blob with FileReader shouldn't throw.  It should just fail with
onerror.  Developers shouldn't have to write two different error handlers to
use FileReader, using two completely different mechanisms (exceptions and error
events).

I agree that close() shouldn't throw, either.  The blob is in the state the
developer wanted--closed--so it'll just make everyone wrap blob.close() in an
empty try/catch.

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

Received on Thursday, 27 March 2014 14:48:19 UTC