Closed Djuffin closed 3 months ago
Hi @Djuffin
My apologies it's taken us so long to get back to you on this. I realize things may have moved on significantly since you filed this review. We did have a fairly detailed discussion on this review in October but unfortunately the output didn't make its way into this issue. Specifically you've asked "Should we just use a boolean value instead of a transfer list to indicate transferring of the ArrayBuffer contents to a WebCodecs object". In the absence of our feedback have you made any decision in the group thus-far on this? In any case, we don't see any issues and we're happy with the multi-stakeholder story here.
Thank you!
The change has been merged to the webcodecs spec and released in Chromium
Thanks @Djuffin we're happy to close on this basis.
こんにちは TAG-さん!
I'm requesting a TAG review of "Allow transferring ArrayBuffer into WebCodecs object constructors".
We're working on adding transferable buffers to WebCodecs object constructors. We've copied the transfer-list approach used by structuredClone and postMessage.
However a concern have been raised that this mechanism isn't ideal: Should we just use a boolean value instead of a transfer list to indicate transferring of the ArrayBuffer contents to a WebCodecs object. Arguments:
We've been asked to solicit TAG guidance on whether copying this mechanism is appropriate in terms of TAG principles around consistency.
Further details:
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify @Djuffin