Skip to content
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

Safari 18 drops JPEG 2000 support #7095

Merged
merged 1 commit into from
Jun 16, 2024
Merged

Safari 18 drops JPEG 2000 support #7095

merged 1 commit into from
Jun 16, 2024

Conversation

Schweinepriester
Copy link
Contributor

https://webkit.org/blog/15443/news-from-wwdc24-webkit-in-safari-18-beta/

Images

WebKit for Safari 18 beta removes support for the JPEG2000 image format. Safari was the only browser to ever provide support.

If you've been serving JPEG2000 files using best practices, then your site is using the picture element to offer multiple file format options to every browser. Safari 18 beta will simply no longer choose JPEG2000, and instead use a file compressed in JPEG XL, AVIF, WebP, HEIC, JPG/JPEG, PNG, or Gif --- choosing the file that's best for each user. Only one image will be downloaded when you use <picture>, and the browser does all the heavy lifting.

We have noticed that some Content Deliver Networks (CDN) use User Agent sniffing to provide one file to each UA, offering only JPEG2000 images to Safari --- especially on iPhone and iPad. If you expect this might be happening with your site, we recommend testing in Safari 18 beta on both macOS Sequoia and iOS or iPadOS 18. If you see problems, contact your SaaS provider or change your image delivery settings to ensure your website provides fallback images using industry best practices.

If you notice a broken site, please file an issue at webcompat.com.

@Fyrd
Copy link
Owner

Fyrd commented Jun 16, 2024

RIP JPEG 2000 I guess!

Thanks!

@Fyrd Fyrd merged commit 8dc996b into Fyrd:main Jun 16, 2024
1 check passed
@Schweinepriester Schweinepriester deleted the patch-1 branch June 16, 2024 17:51
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.

2 participants