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

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

--- Comment #26 from Glenn Maynard <glenn@zewt.org> ---
(In reply to Arun from comment #25)
> (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.

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

It's relevant because of the "these two things being different is confusing"
argument.

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

Received on Wednesday, 2 April 2014 21:12:29 UTC