[Bug 25343] Expose an isClosed property on Blob Objects

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

--- Comment #20 from Glenn Maynard <glenn@zewt.org> ---
(In reply to Jonas Sicking from comment #16)
> I.e. while it's easy for us to say that you could always do
> 
> someObj.the_blob.close();
> someObj.the_blob = null;
> 
> things might not be as simple in all web apps. I.e. maybe there might be a
> whole host of "someObj" objects that all point to the same blob. Tracking
> all of them down might add considerable complexity.

Closing blobs isn't a mechanism to shut actions down on a blob, because it
doesn't propagate to slices or structured clones--you may have a whole host of
*slices* of the blob--and it doesn't affect ongoing async operations (closing a
resource immediately after starting a read, before the read finishes, looks
like a basic pattern).  close() is just a mechanism to allow storage to be
freed deterministically, not a way to signal your own code to stop doing
something.

There are no use cases for this, so it's just interface bloat, and may
encourage people to misinterpret the point of closing blobs.

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

Received on Friday, 16 May 2014 21:29:13 UTC