W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

[Bug 16952] Add a Blob.close()

From: <bugzilla@jessica.w3.org>
Date: Mon, 02 Jul 2012 06:16:14 +0000
Message-Id: <E1SlZvi-0002dy-1O@jessica.w3.org>
To: public-webapps@w3.org

Simon Pieters <simonp@opera.com> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #5 from Simon Pieters <simonp@opera.com> 2012-07-02 06:16:29 UTC ---
The spec should say that size must return 0 if the Blob is neutered (is
consistent with ArrayBuffer). (Please specify this at #dfn-size.)

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

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

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

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 2 July 2012 06:16:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:37 UTC