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 > > On Wed, Jan 15, 2020 at 6:28 PM Jon Bauman <jbau...@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. > > > > [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 > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
