- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 Jul 2012 19:52:30 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16952 --- Comment #18 from Arun <arun@mozilla.com> 2012-07-12 19:52:30 UTC --- (In reply to comment #17) > The thing is that a Blob can generally be passed around through a lot of parts > of a code-base due to it's mostly-readonly nature. > > This could mean that just because part of the code closes a Blob, doesn't > always mean that another part of the code which has a reference to the same > Blob, is always aware. Which I think is fine, and independent of our discussion about whether or not to throw, no? This is similar to reads which are already underway: technically, such reads are "unaware" that a Blob has had close() called on it and is thus neutered, which is why we allow them to go through. Operations which begin anew on a neutered Blob (and thus, operations which are "aware" of the fact that the Blob is neutered) throw. Or have I missed something? -- 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 Thursday, 12 July 2012 19:52:31 UTC