[Bug 16952] Add a Blob.close()

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

--- Comment #6 from Arun <arun@mozilla.com> 2012-07-03 14:47:18 UTC ---
(In reply to comment #5)
> The spec should say that size must return 0 if the Blob is neutered (is
> consistent with ArrayBuffer). (Please specify this at #dfn-size.)
> 

OK.

> I'm not happy with async reads being successful for neutered Blobs. If Blobs
> are made Transferable, and gets transfered mid-read, it would mean you have to
> make a copy anyway. I would prefer if async reads fail if the Blob gets
> neutered.

But what if a read has already been initiated?  I think this requirement is for
reads that are underway.  Are you ok with *that*?  If so, that should be made
more clear.  

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

> The requirement about sync read methods should be removed since it can't happen
> to begin with.
> 

OK.

> "dereferencing a Blob URI bound to a Blob object on which close has been called
> results in a 500 Error." this part should be made a requirement (preferably in
> the part of the spec where dereferencing a Blob URI is defined).

OK.

-- 
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 14:47:24 UTC