Skip to content

remove the definition of the image/avif-sequence MIME type #86

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 18, 2020

Conversation

cconcolato
Copy link
Collaborator

@cconcolato cconcolato commented Jun 17, 2020

Closes #59


Preview | Diff

@cconcolato
Copy link
Collaborator Author

We probably need to do a version change like v1.0.1 and change the date. Any view on that? I'll do that as a final step before merging.

@aklemets
Copy link
Contributor

Updating the spec to v1.0.1 sounds fine to me.

@negge
Copy link
Collaborator

negge commented Jun 22, 2020

Depending on how significant any normative changes are, we may want to consider using the same updated version as the AV1 spec:

Version 1.0.0 with Errata 1

pull bot pushed a commit to Alan-love/chromium that referenced this pull request Jun 27, 2020
The AOMedia Image Working Group decided to remove the
"image/avif-sequence" MIME type and the "avifs" file extension from the
AVIF specification:
AOMediaCodec/av1-avif#59
AOMediaCodec/av1-avif#86

Since the future of the "image/avif-sequence" MIME type and the "avifs"
file extension is uncertain, it is best to remove them from the Chromium
source tree until the dust settles.

Test:
net_unittests --gtest_filter=MimeUtilTest.*
blink_common_unittests --disable-features=AVIF
blink_common_unittests --enable-features=AVIF
blink_platform_unittests --gtest_filter=*AVIF*

Bug: 1099839
Change-Id: I245e1ee2240bba315a49555908036eba7219afd6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2270670
Commit-Queue: Wan-Teh Chang 
Reviewed-by: Ryan Sleevi 
Reviewed-by: Peter Kasting 
Reviewed-by: Dale Curtis 
Cr-Commit-Position: refs/heads/master@{#783192}
@cconcolato cconcolato merged commit 45d9ea6 into master Aug 18, 2020
@cconcolato cconcolato deleted the mime_type_fix branch October 27, 2020 17:37
pull bot pushed a commit to Mu-L/chromium that referenced this pull request Nov 11, 2020
The image/avif-sequence MIME type and the associated file extension
"avifs" have been removed from the AVIF specification. See
AOMediaCodec/av1-avif#59
AOMediaCodec/av1-avif#86

Add "-animated-" to the filenames so it's clear they are animated images.

Change-Id: Ifd46d9c40430a5a60ada28fdede0cb232f56f75f
Bug: 1147501
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528169
Commit-Queue: Wan-Teh Chang 
Commit-Queue: Peter Kasting 
Reviewed-by: Peter Kasting 
Reviewed-by: Stephen Chenney 
Reviewed-by: Dale Curtis 
Cr-Commit-Position: refs/heads/master@{#825937}
copybara-service bot pushed a commit to ChromeDevTools/devtools-frontend that referenced this pull request Feb 23, 2023
The separate `image/avif-sequence` MIME type was removed [1]. This
patch updates our mappings accordingly.

[1]: AOMediaCodec/av1-avif#86

Bug: chromium:1207353
Change-Id: I3879b7f470693574998383a5a9bd0559d155e146
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4285221
Commit-Queue: Ergün Erdoğmuş 
Auto-Submit: Mathias Bynens 
Reviewed-by: Ergün Erdoğmuş 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Potential issues with two MIME types
3 participants