Intent to Ship: AVIF Decode
Jai Krishnan
Contact emails
ja...@google.com, w...@google.com, dalec...@google.com
Specification
https://aomediacodec.github.io/av1-avif/
Tag Review
Since the specification was already developed in another organization, blink-api-owners determined that a TAG review would not be required.
Summary
Enable native AVIF decode support (with the existing AV1 video decoder).
Link to “Intent to Prototype” blink-dev discussion
Intent to Prototype Discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
The feature is starting support on Windows, Mac, Linux, and ChromeOS - eventually but not immediately on Android and Android WebView. Support will be gated on a DFM for the AV1 decoder, with default native support across desktop platforms (Windows, Mac, Linux, ChromeOS). If AV1 gets default support on Android via increased demand outweighing binary size and expected performance limitations on smartphones (battery drain considerations, etc), the support would extend to AVIF on Android as well.
Demo link
Link-U Demo Page
Netflix Demo Images
Debuggability
N/A
Risks
Interoperability and Compatibility
Edge: Public support
Firefox:In development
Safari:No signals
Web / Framework developers: Active interest on crbug
Ergonomics
N/A
Activation
Active library work related to this feature already exists - AVIF decode implementations through libavif are working with multiple AV1 video decoders, and there are multiple related new open and closed source projects in development.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
Tracking progress at crbug.com/1099028
Entry on the feature dashboard
https://chromestatus.com/feature/4905307790639104
Yoav Weiss
Contact emails
ja...@google.com, w...@google.com, dalec...@google.com
Specification
https://aomediacodec.github.io/av1-avif/
Tag Review
Since the specification was already developed in another organization, blink-api-owners determined that a TAG review would not be required.
Summary
Enable native AVIF decode support (with the existing AV1 video decoder).
Link to “Intent to Prototype” blink-dev discussion
Intent to Prototype Discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
The feature is starting support on Windows, Mac, Linux, and ChromeOS - eventually but not immediately on Android and Android WebView. Support will be gated on a DFM for the AV1 decoder, with default native support across desktop platforms (Windows, Mac, Linux, ChromeOS). If AV1 gets default support on Android via increased demand outweighing binary size and expected performance limitations on smartphones (battery drain considerations, etc), the support would extend to AVIF on Android as well.
Demo link
Link-U Demo Page
Netflix Demo Images
Debuggability
N/A
Risks
Interoperability and Compatibility
Edge: Public support
Firefox:In development
Safari:No signals
Web / Framework developers: Active interest on crbug
Ergonomics
N/A
Activation
Active library work related to this feature already exists - AVIF decode implementations through libavif are working with multiple AV1 video decoders, and there are multiple related new open and closed source projects in development.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
Tracking progress at crbug.com/1099028
Entry on the feature dashboard
https://chromestatus.com/feature/4905307790639104
--
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/CAM52mscXBba7sSXUWaWqrYxxzJ4X%3DpRa68w%2BowXH1F4T0GM2DA%40mail.gmail.com.
PhistucK
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEgX57UX-G4%2B5f%2BaR3JJUdf6N63LF39OSnT%2B3Jt-O65%3D8g%40mail.gmail.com.
Yoav Weiss
This fragmentation is very problematic if you are not going to be adding the MIME type to the Accept HTTP header, encouraging even more specific user agent sniffing (not only the Chrome version, but also the platform).
Chris Harrelson
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEgEDuZKXsaogcBf-aSej4VtOjQDUc7xbgH65qDgJVZ0kw%40mail.gmail.com.
Daniel Bratell
LGTM3
A pity it won't be on Android but I understand the reasons which
I hope will be temporary.
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_ZNj1h1FzKBhkrM7yEZDy%3DawV06YiLpSr%2Bn%2Bd0O57Rtg%40mail.gmail.com.
Dale Curtis
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/82545846-bb0f-c67a-8faa-8696172e1bef%40gmail.com.