[Bug 23416] Introduce new concept of neutered

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

--- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 7 October 2013 22:33:30 UTC