This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/multipage/infrastructure.html Multipage: https://html.spec.whatwg.org/multipage/#concept-transferable-neutered Complete: https://html.spec.whatwg.org/#concept-transferable-neutered Referrer: https://html.spec.whatwg.org/multipage/ Comment: ES6 renamed "neutered" to "detached". Posted from: 46.127.136.57 by annevk@annevk.nl User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:35.0) Gecko/20100101 Firefox/35.0
The term "neutered" is defined in the HTML spec. It's an HTML spec term of art. What does it means for ES6 to rename it?
It means the text in that section I pointed to is no longer accurate as ES6 defines ArrayBuffer and I don't think IDL papers over that aspect.
The action to be taken here, I think, is that HTML should invoke the "DetachArrayBuffer" abstract operation (https://people.mozilla.org/~jorendorff/es6-draft.html#sec-detacharraybuffer) on the old buffer.
I looked into fixing this and it's actually rather involved since HTML uses "neutered" as a generic concept shared across several elements, whereas ECMAScript only has one set of objects that have it. So some new kind of abstraction would be needed.
https://github.com/whatwg/html/pull/727