Thanks both for the analysis here. I think we want to align with Chrome, that has a behaviour that I find sensible. Simplifying the test case to: ```js var buf = new ArrayBuffer(new Uint8Array(4)); window.postMessage(buf) VideoDecoder.isConfigSupported({"codec": "vp8", "description":buf}) ``` it says: ``` Uncaught (in promise) TypeError: Failed to execute 'isConfigSupported' on 'VideoDecoder': description is detached. ``` I've filed https://github.com/w3c/webcodecs/issues/762 to make the spec clear, and I'll write a patch for our implementation to align.
Bug 1874293 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks both for the analysis here. I think we want to align with Chrome, that has a behaviour that I find sensible. Simplifying the test case to: ```js var buf = new ArrayBuffer(4); buf.transferToFixedLength() VideoDecoder.isConfigSupported({"codec": "፝a", "description":buf}) ``` it says: ``` Uncaught (in promise) TypeError: Failed to execute 'isConfigSupported' on 'VideoDecoder': description is detached. ``` I've filed https://github.com/w3c/webcodecs/issues/762 to make the spec clear, and I'll write a patch for our implementation to align.