27031 2014-10-13 15:11:38 +0000 ES6 renamed "neutered" to "detached". 2016-02-23 17:35:07 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED https://html.spec.whatwg.org/#concept-transferable-neutered P3 normal Unsorted 27030 1 contributor ian adamk annevk ian mike contributor oldest_to_newest 113025 0 contributor 2014-10-13 15:11:38 +0000 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 114696 1 ian 2014-11-07 22:38:28 +0000 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? 114709 2 annevk 2014-11-08 08:02:59 +0000 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. 120279 3 adamk 2015-05-13 00:34:18 +0000 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. 123206 4 annevk 2015-09-15 15:15:21 +0000 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. 125241 5 annevk 2016-02-23 17:35:07 +0000 https://github.com/whatwg/html/pull/727