Bug 222971

(In reply to Ewout ter Hoeven from comment #0) > Created attachment 422690 [details] > dav1d 0.8.2 patch > > Updates dav1d from 0.7.0 to 0.8.2, improving decoding speed, reducing CPU > usage and improving security. Patch is attached. > > dav1d changelog: https://code.videolan.org/videolan/dav1d/-/blob/master/NEWS Thanks for this a heads up. AVIF support in webkit is experimental, not for production. Definitely, we will consider bumping up the versions of libavif and dav1d.

ChangeLog needed! See https://webkit.org/contributing-code/ for the whole procedure.

Also most of our (GTK/WPE) build bots now rely on the Flatpak SDK for dependencies. It's less easier to update though, I can take care of it in a follow-up patch.

(In reply to ChangSeok Oh from comment #1) > (In reply to Ewout ter Hoeven from comment #0) > > Created attachment 422690 [details] > > dav1d 0.8.2 patch > > > > Updates dav1d from 0.7.0 to 0.8.2, improving decoding speed, reducing CPU > > usage and improving security. Patch is attached. > > > > dav1d changelog: https://code.videolan.org/videolan/dav1d/-/blob/master/NEWS > > Thanks for this a heads up. AVIF support in webkit is experimental, not for > production. Definitely, we will consider bumping up the versions of libavif > and dav1d. Maybe we can consider enabling it by default for the next cycle though? 2.34 scheduled for September/October 2021.

I used the GitHub mirror to create and test this patch, haven't used SVN before, if someone could generate a ChangeLog file for me that would be awesome, otherwise I will dive in next week. It's a very small change, so if anyone wants to patch it themselves using the correct WebKit procedures, feel free to do so. Targeting AVIF support enabled by default would be a great goal! It's tricky though, and will need a lot of testing, Firefox had to roll back for the 86 release for example: https://bugzilla.mozilla.org/show_bug.cgi?id=1682995#c22 Should we create a tracking issue for enabling AVIF decoding by default?

(In reply to Ewout ter Hoeven from comment #5) > I used the GitHub mirror to create and test this patch, haven't used SVN > before, if someone could generate a ChangeLog file for me that would be > awesome, otherwise I will dive in next week. It's a very small change, so if > anyone wants to patch it themselves using the correct WebKit procedures, > feel free to do so. There is a Tools/Scripts/prepare-changelogs script. It will create the skeleton that you need to fill.

<rdar://problem/75475659>

This was handled in https://bugs.webkit.org/show_bug.cgi?id=224177, so changing the status of this bug in RESOLVED FIXED. Thanks for the effort Philippe!