Intent to Ship: AVIF Decode

408 views
Skip to first unread message

Jai Krishnan

unread,
Jun 25, 2020, 1:15:39 AM6/25/20
to blin...@chromium.org

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

unread,
Jun 25, 2020, 1:55:15 AM6/25/20
to Jai Krishnan, blink-dev
LGTM1

On Thu, Jun 25, 2020 at 7:15 AM 'Jai Krishnan' via blink-dev <blin...@chromium.org> wrote:

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


Have we reached out? If not, would be good to do so.
 

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

unread,
Jun 25, 2020, 6:54:43 AM6/25/20
to Yoav Weiss, Jai Krishnan, blink-dev
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).

PhistucK


Yoav Weiss

unread,
Jun 25, 2020, 7:42:45 AM6/25/20
to PhistucK, Jai Krishnan, blink-dev
On Thu, Jun 25, 2020 at 12:54 PM PhistucK <phis...@gmail.com> wrote:
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).

This was discussed at the I2P and AFAIK, addressed by adding the MIME type to both `Accept` headers and to `type` attribute processing.

Chris Harrelson

unread,
Jun 25, 2020, 3:35:30 PM6/25/20
to Yoav Weiss, PhistucK, Jai Krishnan, blink-dev

Daniel Bratell

unread,
Jun 25, 2020, 5:04:14 PM6/25/20
to Chris Harrelson, Yoav Weiss, PhistucK, Jai Krishnan, blink-dev

LGTM3

A pity it won't be on Android but I understand the reasons which I hope will be temporary.

/Daniel

Dale Curtis

unread,
Jun 25, 2020, 5:22:40 PM6/25/20
to Daniel Bratell, Chris Harrelson, Yoav Weiss, PhistucK, Jai Krishnan, blink-dev
https://bugs.chromium.org/p/chromium/issues/detail?id=1003535 tracks the AV1 via DFM work on Android for those who want to follow along.

- dale

Reply all
Reply to author
Forward
0 new messages