[Bug 25343] Expose an isClosed property on Blob Objects

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

--- Comment #10 from Arun <arun@mozilla.com> ---
(In reply to Simon Pieters from comment #8)
> (In reply to Arun from comment #6)
> > I'd like other use cases, too, but I think it's useful to have.
> 

> In the game scenario with textures, the use case is adequately handled by
> losing the reference to the blob, as Glenn pointed out.


Yes, a "workaround" to my example using null/losing references is possible. But
losing the reference is *semantically different* than closing a Blob. Losing a
reference makes slice() calls fail by definition, but closing a Blob means you
can still slice() it, and even coin a Blob URL on it (but that Blob URL will
return a network error).

> 
> Are there other use cases?


So, this could be the rub. As Glenn points out, this is definitely a "it seems
like a good idea" situation (over IRC). Developers *should* be able to tell why
certain operations fail. I feel like there are other use cases, since I feel
strongly that we should allow developers to test for closed Blobs. I agree with
backing this out if we do an inadequate job of proving my point, though.

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

Received on Wednesday, 7 May 2014 03:18:00 UTC