Edge 116 Insider also supports AVIF #6809
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#6788
By adding the tentative entry of 116, It seems as if Edge had quit supporing AVIF even in Insider builds.
However Edge 116 Insider does continue supporting AVIF under that condition.
This PR must be merged until the upcoming entry of 117 is added.
The "File changed" tab shows this PR only affects one line.
Note
it looks like the current Canary build (118) now lacks the support even with the flag in WIndows 11 stable.
Dev (117) still has the support.
Therefore, we have to change the footnote in 118.
The condition has been discussed in #6810.