This will allow detaching array buffers and using corresponding buffers inside VideoFrame, ImageDecoder, EncodedVideoChunk, EncodedAudioChunk, AudioData without a copy.
None
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
Shipping on desktop | 120 |
Shipping on Android | 120 |
Hi Eugene,Just to double check. Once an ArrayBuffer is transferred and detached, any further access will result in some sort of TypeError, right?Thanks,Jonathan
On Wednesday, August 16, 2023 at 10:22:00 PM UTC+1 Eugene Zemtsov wrote:
Contact emailsezem...@google.com
Explainerhttps://gist.github.com/Djuffin/1c8fac486ca9f402be85074166e89a16
Specificationhttps://www.w3.org/TR/webcodecs/#dictdef-videoframeinit
SummaryThis will allow detaching array buffers and using corresponding buffers inside VideoFrame, ImageDecoder, EncodedVideoChunk, EncodedAudioChunk, AudioData without a copy.
Blink componentBlink>Media>WebCodecs
TAG reviewNone
Risks
Interoperability and CompatibilityNone
Gecko: N/A (https://www.w3.org/2023/05/30-mediawg-minutes.html#t01) Change is too small to justify this effort. The change was discussed and approved by the w3c media working group.
WebKit: N/A (https://www.w3.org/2023/05/30-mediawg-minutes.html#t01) Change is too small to justify this effort. The change was discussed and approved by the w3c media working group.
Web developers: No signals
Other signals:
WebView application risksDoes this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
DebuggabilityNone
Is this feature fully tested by web-platform-tests?No
Flag name on chrome://flagsNone
Finch feature nameNone
Non-finch justificationNone
Requires code in //chrome?False
Tracking bughttps://crbug.com/1446808
Estimated milestonesShipping on desktop120Shipping on Android120
--Thanks,Eugene Zemtsov.
Thanks for the clarification!On Tue, Aug 22, 2023 at 9:20 PM Eugene Zemtsov <ezem...@google.com> wrote:And it's already a part of the WebCodecs spec.
In addition to Alex's question, I also noticed that you answered the web-platform-tests with a "no", which is a bit unexpected to me. Is there a reason this cannot or won't be tested in web-platform-tests?
/Daniel
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ca4852cc-e0ab-4685-99d9-84d2f8316b90n%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fbe4d8ba-2d6a-f085-6608-25a2eeef6d22%40gmail.com.
On Aug 31, 2023, at 7:14, 'Eugene Zemtsov' via blink-dev <blin...@chromium.org> wrote:
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK8JDrF_jrf-1aRNk1AshPHDzUsiJeS3zoeuwXwuznZMpJxx_w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfX1Vd7t%3DpFtYTB0gojxEBL92Uaj73xt5o63FCTw5hRcZA%40mail.gmail.com.
LGTM3
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_xc8E0%2BrhP322Gaym3-yi1Z_k5y9po%2BM4OsW0CcRQW-A%40mail.gmail.com.