Something is off about this. > Plot twist; here was never a gAMA chunk to begin with! But I do see a gAMA chunk in the file? > 00 00 00 04 67 41 4d 41 00 03 5b 5e 5c ff 26 78 Which decodes to a value of 2.19998. Conversely, I don't see any bundled ICC profiles (iCCP chunks). Mind you, I am able to reproduce the different colors, so something is indeed wrong. Chrome (Windows) and the Photos app (MS Store) both present…
By definition any chunk beginning with a lowercase is optional. I’m just surprised gamma is considered optional.
PNG in Chrome shows a different image than in Safari or any desktop app
31–40 of 49 posts
Re: PNG in Chrome shows a different image than in Safari or any desktop app
#32(I'm running Brave Mobile if that matters. I'm curious if the thumbnail is rendered differently on other mobile web browsers as well?)
Re: PNG in Chrome shows a different image than in Safari or any desktop app
#33Earlier quoted context omitted.
"correct" in fail, in the same way across browsers? that's hilarious. I forget that throughout the history of the internet the one thing we've been able to depend on is different browsers behaving the same way
interoperability of web features has never been this good and it's only getting better https://wpt.fyi/interop-2025 other than the Manifest v3 fiasco, we're probably living in the golden age of web interop
For example, JPEG XL has been proposed for Interop a few times before, but never selected. Therefore, Safari remains the only major browser to support it so far.
Re: PNG in Chrome shows a different image than in Safari or any desktop app
#34Something is off about this. > Plot twist; here was never a gAMA chunk to begin with! But I do see a gAMA chunk in the file? > 00 00 00 04 67 41 4d 41 00 03 5b 5e 5c ff 26 78 Which decodes to a value of 2.19998. Conversely, I don't see any bundled ICC profiles (iCCP chunks). Mind you, I am able to reproduce the different colors, so something is indeed wrong. Chrome (Windows) and the Photos app (MS Store) both present…
Re: PNG in Chrome shows a different image than in Safari or any desktop app
#35Earlier quoted context omitted.
"correct" in fail, in the same way across browsers? that's hilarious. I forget that throughout the history of the internet the one thing we've been able to depend on is different browsers behaving the same way
interoperability of web features has never been this good and it's only getting better https://wpt.fyi/interop-2025 other than the Manifest v3 fiasco, we're probably living in the golden age of web interop
Re: PNG in Chrome shows a different image than in Safari or any desktop app
#36Earlier quoted context omitted.
Another good test page for the browser: https://www.color.org/version4html.xalter
Where, for reference, Safari shows an image that matches the first one listed—meaning, at least in theory, that it fully supports ICC profiles.
Re: PNG in Chrome shows a different image than in Safari or any desktop app
#37Earlier quoted context omitted.
By definition any chunk beginning with a lowercase is optional. I’m just surprised gamma is considered optional.
Right, I guess that's our full story then. I further found some quibbles about that chunk being historically fraught specifically, so many decoders would intentionally ignore it under specific circumstances. I guess this file met the criteria.
Re: PNG in Chrome shows a different image than in Safari or any desktop app
#38Re: PNG in Chrome shows a different image than in Safari or any desktop app
#39Re: PNG in Chrome shows a different image than in Safari or any desktop app
#40Earlier quoted context omitted.
interoperability of web features has never been this good and it's only getting better https://wpt.fyi/interop-2025 other than the Manifest v3 fiasco, we're probably living in the golden age of web interop
Ugh, I hate toggle switches like the Stable/Experimental one. Which one is selected? I can’t tell. Which one of them has the better results?
Every year the major browsers get together and agree on a set of "focus areas" that are paint points for browser interoperability. They've been doing it since 2021. I posted the 2025 results. All browsers reached about 99% support for the selected features
The features are voted on by web developers. Basically anyone with a GitHub account can get involved. Here's a blog post with more info about the process https://webkit.org/blog/17320/submit-your-ideas-for-interop-...