- From: <bugzilla@jessica.w3.org>
- Date: Thu, 31 Oct 2013 22:59:07 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23416
Arun <arun@mozilla.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Arun <arun@mozilla.com> ---
(In reply to Ian 'Hixie' Hickson from comment #11)
> The concept of "neutered" in the Transferable sense is "this can't be
> transferred any more". Anything that isn't Transferable is always in that
> state, so it doesn't make sense to talk about other things being neutered in
> the Transferable sense.
>
> If File and Blob should be Transferable (meaning they can't be cloned, or
> that cloning them is an expensive operation), then that's a different
> matter. My understanding is that that is not the case currently.
>
>
> I really don't understand the problem here. It's fine to be able to send the
> object into a different state. Lots of objects do this. WebSocket objects
> can get closed. Windows can get closed. XMLHttpRequest objects can go into
> several states. And so on.
Blobs aren't going to be Transferable -- they don't need to be.
You're right: it isn't a big deal to roll a new one.
http://dev.w3.org/2006/webapi/FileAPI/#dfn-close
Marking this fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 31 October 2013 22:59:09 UTC