Re: [heycam/webidl] Who uses the detach concept for ArrayBuffer? (#724)

I looked at where detaching actually happens in the Gecko implementation.  Looks like it happens in the following places:

1) Structured cloning.  In spec terms, looks like https://html.spec.whatwg.org/multipage/structured-data.html#structuredserializewithtransfer calls https://tc39.github.io/ecma262/#sec-detacharraybuffer directly.

2) WASM memory-wrangling bits.  In spec terms, I _think_ those bottom out in https://webassembly.github.io/spec/js-api/index.html#reset-the-memory-buffer which calls https://tc39.github.io/ecma262/#sec-detacharraybuffer directly.

3) Various Web Audio bits.  https://webaudio.github.io/web-audio-api/#dom-baseaudiocontext-decodeaudiodata calls https://tc39.github.io/ecma262/#sec-detacharraybuffer directly.  So does <https://webaudio.github.io/web-audio-api/#acquire-the-content>.  Filed https://github.com/WebAudio/web-audio-api/issues/1862 on the one underdefined bit and https://github.com/WebAudio/web-audio-api/issues/1863 on the fact that they don't handle the throwing parts well.

As far as I can tell, that's it.  There might, of course, be uses in drafts or specs that Gecko does not implement.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/724#issuecomment-491289712