Intent to implement: AVIF (AV1 Image Format) support

[Jon Bauman]

AVIF is an image format based on the AV1 video codec [1] from the Alliance
for Open Media [2]. AV1 support shipped in release 55 [3] and is currently
supported in Chrome, but not Safari. There is an open issue for AVIF
support in Chrome [4].

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=avif

Standard: https://aomediacodec.github.io/av1-avif/

Platform coverage: All

Restricted to secure contexts: No. There's currently no mechanism to
enforce this for image formats, but we can revisit this before enabling
this by default. The same goes for CORS.

Target Release: 76

Preference behind which this will be implemented: image.avif.enabled,
turned off by default.

[1] https://en.wikipedia.org/wiki/AV1
[2] https://aomedia.org/
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=av1
[4] https://bugs.chromium.org/p/chromium/issues/detail?id=960620

[Jon Bauman]

This will use the same library for decoding. The tentative plan is to use a
similar approach and do the decoding itself in a remote process (RDD), but
this will be the first image format (as opposed to audio/video) to use the
media decoding stack, so plans are still somewhat fluid.

On Wed, Jan 15, 2020 at 1:05 PM Tom Ritter <t...@mozilla.com> wrote:

> We sandboxed av1 into its own process for security concerns.
> Presumably this is using the same or a similar library; so do we have
> plans for mitigating the same concern before rolling out to users?
>
> -tom

> > _______________________________________________
> > dev-platform mailing list
> > dev-pl...@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/dev-platform
>

[James Graham]

On 13/01/2020 21:48, Jon Bauman wrote:
> AVIF is an image format based on the AV1 video codec [1] from the Alliance
> for Open Media [2]. AV1 support shipped in release 55 [3] and is currently
> supported in Chrome, but not Safari. There is an open issue for AVIF
> support in Chrome [4].
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=avif
>
> Standard: https://aomediacodec.github.io/av1-avif/
>
> Platform coverage: All
>
> Restricted to secure contexts: No. There's currently no mechanism to
> enforce this for image formats, but we can revisit this before enabling
> this by default. The same goes for CORS.
>
> Target Release: 76
>
> Preference behind which this will be implemented: image.avif.enabled,
> turned off by default.

Is there some kind of cross-implementation testsuite for this format? Or
how are we confident that we won't end up in a scenario where Chrome and
Gecko have observable differences in their handling of AVIF?

[Martin Thomson]

This sounds good. In the interests of transparency, it might be good to
get this (and AV1 even) added to our standards positions repo (
https://mozilla.github.io/standards-positions/). I don't know if this
necessarily rises to "important" in the same way that AV1 does, but it
would be good to have a clear signal from us that other browsers can use in
their decision making.

On Thu, Jan 16, 2020 at 5:27 AM Jon Bauman <jba...@mozilla.com> wrote:

> AVIF is an image format based on the AV1 video codec [1] from the Alliance
> for Open Media [2]. AV1 support shipped in release 55 [3] and is currently
> supported in Chrome, but not Safari. There is an open issue for AVIF
> support in Chrome [4].
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=avif
>
> Standard: https://aomediacodec.github.io/av1-avif/
>
> Platform coverage: All
>
> Restricted to secure contexts: No. There's currently no mechanism to
> enforce this for image formats, but we can revisit this before enabling
> this by default. The same goes for CORS.
>
> Target Release: 76
>
> Preference behind which this will be implemented: image.avif.enabled,
> turned off by default.
>

[Tom Ritter]

We sandboxed av1 into its own process for security concerns.
Presumably this is using the same or a similar library; so do we have
plans for mitigating the same concern before rolling out to users?

-tom

[Jon Bauman]

I'm not aware of any cross-implementation testsuite, but I agree it would
be valuable. I suppose that would fall under the responsibility of the
specification, so I could file an issue in the AVIF spec repo (
https://github.com/AOMediaCodec/av1-avif/issues/), unless anyone has other
suggestions.

On Thu, Jan 16, 2020 at 7:50 AM James Graham <ja...@hoppipolla.co.uk> wrote:

> On 13/01/2020 21:48, Jon Bauman wrote:
> > AVIF is an image format based on the AV1 video codec [1] from the
> Alliance
> > for Open Media [2]. AV1 support shipped in release 55 [3] and is
> currently
> > supported in Chrome, but not Safari. There is an open issue for AVIF
> > support in Chrome [4].
> >
> > Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=avif
> >
> > Standard: https://aomediacodec.github.io/av1-avif/
> >
> > Platform coverage: All
> >
> > Restricted to secure contexts: No. There's currently no mechanism to
> > enforce this for image formats, but we can revisit this before enabling
> > this by default. The same goes for CORS.
> >
> > Target Release: 76
> >
> > Preference behind which this will be implemented: image.avif.enabled,
> > turned off by default.
>

> Is there some kind of cross-implementation testsuite for this format? Or
> how are we confident that we won't end up in a scenario where Chrome and
> Gecko have observable differences in their handling of AVIF?