[Bug 16952] Add a Blob.close()

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

--- Comment #8 from Simon Pieters <simonp@opera.com> 2012-07-03 15:59:20 UTC ---
(In reply to comment #6)
> But what if a read has already been initiated?  I think this requirement is for
> reads that are underway.  Are you ok with *that*?

No. I think it should fail in that case. Similarly as if the user removes a
file from disk while the browser is reading it. It seems the async read
algorithm doesn't actually step through the fail steps after the read has
started, currently, but it should, right?

> I wonder now if we should keep a flag that indicates neutered on a Blob.

That works. The ArrayBuffer spec seems to just reference "neutered" and use it
as a flag.

(In reply to comment #7)
> Another important thing to note is that Blob is not Transferable -- we're
> merely cribbing from HTML5's concept of neutered objects, without taking the
> notion of Transferable interfaces over.

But we should make sure that it can be made Transferable in the future and
ideally let it have the same semantics as close() wrt neutered, IMHO.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 3 July 2012 15:59:22 UTC