Add AVIF MIME type support to mimetype definitions #15739
+1
−0
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
AVIF images will open, rather than download, as the default behaviour.
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.
Currently AVIF images (added in cde35be) will download, rather than open, as the default behaviour. Turns out we need to add it as a valid MIME type so it acts like other image types.
Description
Simple change to
ui.pyto addimage/avifas a valid MIME type, likeimage/webpcurrently is. Without this, AVIF images will be downloaded, rather than opened, by certain browsers (at least, that was the behaviour for Chrome 124.0.6367.119 on Windows 11).Screenshots/videos:
Checklist: