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

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

--- Comment #25 from Arun <arun@mozilla.com> ---
(In reply to Glenn Maynard from comment #23)
> (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 with this. In fact, FileReader should *only throw* when it is invalidly
invoked per spec.; that is, if it is in the LOADING state, preventing multiple
invocation of an "in-use" FileReader. But it shouldn't throw when reading a
Blob; it shouldn't throw on a CLOSED blob.


> 
> 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.

This is a bit less obvious to me, but this bug is about URL.create* on a CLOSED
blob, which shouldn't throw.

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

Received on Wednesday, 2 April 2014 21:05:27 UTC