Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PNG in Chrome shows a different image than in Safari or any desktop app

lr0.org

Post reply on HN
Print view View original

41–49 of 49 posts

Re: PNG in Chrome shows a different image than in Safari or any desktop app

#41

Post by culi »

gcanyon wrote: post #35
culi wrote: post #19

Earlier 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

While not disputing in any way the truth of what you're saying: I'm a product manager who leans toward Safari, while the devs I work with use Chrome almost exclusively, and we have an unwritten agreement that when it comes to display/layout issues, I'll double check in Chrome before filing the bug. It's only been Safari-exclusive a handful of times, but that's enough that it's annoying for everyone when it's just me.

I've run into Safari exclusive issues before as well around color transparency, but tbh I'm surprised it comes up that often. Modern IDEs support linters that warn you whenever you are using a CSS feature that isn't supported by all modern browsers. You can even set the year you wanna support (e.g. all major browser versions since 2023). Between that awesome tooling and rapidly improving browser support for web standards, these kinds of issues feel extremely rare.

Except for printing. Printing has and seemingly always will f'n suck. Unfortunately WPT doesn't have a good way of testing for print-related features

Re: PNG in Chrome shows a different image than in Safari or any desktop app

#42

Post by culi »

F3nd0 wrote: post #33
culi wrote: post #19

Earlier 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

If I’m not mistaken, they only select a couple of features to work on every year—the ones they already agree on to begin with—and the high interoperability shown in the link only concerns those few select features. 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.

Yes exactly. Voting for the 2026 focus areas is happening now btw. The next year's interop usually releases around February

https://webkit.org/blog/17320/submit-your-ideas-for-interop-...

And yes JPEG XL support is often the most requested feature and the major browsers have responded. Google and Firefox are both willing to take it on but Firefox's biggest concern is with the reference decoder which has some major security flaws. They basically want to wait until libjxl/jxl-rs is performant enough

https://github.com/mozilla/standards-positions/pull/1064

Here's the current issue for that proposal if you want to get involved

https://github.com/web-platform-tests/interop/issues/994

Re: PNG in Chrome shows a different image than in Safari or any desktop app

#43

Post by mirashii »

gcanyon wrote: post #36
danaris wrote: post #16

Earlier quoted context omitted.

Where, for reference, Safari shows an image that matches the first one listed—meaning, at least in theory, that it fully supports ICC profiles.

Interesting: for me, the image quadrants display correctly in Safari, but there is a horizontal white line between the top and bottom left quadrants. You're not seeing that?

I see the white line on mobile, but not on desktop, though my OS versions are wildly different too, so hard to narrow down exactly what it might be there.

Re: PNG in Chrome shows a different image than in Safari or any desktop app

#44

Post by danaris »

gcanyon wrote: post #36
danaris wrote: post #16

Earlier quoted context omitted.

Where, for reference, Safari shows an image that matches the first one listed—meaning, at least in theory, that it fully supports ICC profiles.

Interesting: for me, the image quadrants display correctly in Safari, but there is a horizontal white line between the top and bottom left quadrants. You're not seeing that?

I see the white line on Safari, and also on Mac Firefox. No idea what the line means—it's not present in any of the reference images.

Re: PNG in Chrome shows a different image than in Safari or any desktop app

#45

Post by smileybarry »

gcanyon wrote: post #36
danaris wrote: post #16

Earlier quoted context omitted.

Where, for reference, Safari shows an image that matches the first one listed—meaning, at least in theory, that it fully supports ICC profiles.

Interesting: for me, the image quadrants display correctly in Safari, but there is a horizontal white line between the top and bottom left quadrants. You're not seeing that?

The white line is just because the four quadrants are four separate images, and the four images are HTML-aligned together to make one.

Re: PNG in Chrome shows a different image than in Safari or any desktop app

#46

Post by danaris »

gcanyon wrote: post #35
culi wrote: post #19

Earlier 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

While not disputing in any way the truth of what you're saying: I'm a product manager who leans toward Safari, while the devs I work with use Chrome almost exclusively, and we have an unwritten agreement that when it comes to display/layout issues, I'll double check in Chrome before filing the bug. It's only been Safari-exclusive a handful of times, but that's enough that it's annoying for everyone when it's just me.

I guess the question here has to be: is this actually a bug in Safari? Or is it a bug in Chrome, that people (whether that's your people or third parties) have just been working around in a way that doesn't work in Safari?

And this is a big part of the problem with having Chrome become such a dominant force on the web: people assume that it's correct when Safari displays something differently. And people give instructions and documentation for how to do various things "in HTML/CSS/JS" when they've never tested them in anything other than Chrome, so if Chrome's behavior deviates from the spec there, someone implementing those instructions on Safari will see them fail, and assume incorrectly that it's Safari that's wrong.

Note that I am not saying this is what is happening in any specific case—but because Chrome is so dominant, enough people treat it as the de-facto standard that over time, it becomes a near-inevitability that this will happen in some cases.

Re: PNG in Chrome shows a different image than in Safari or any desktop app

#47

Post by F3nd0 »

culi wrote: post #42
F3nd0 wrote: post #33

Earlier quoted context omitted.

If I’m not mistaken, they only select a couple of features to work on every year—the ones they already agree on to begin with—and the high interoperability shown in the link only concerns those few select features. 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.

Yes exactly. Voting for the 2026 focus areas is happening now btw. The next year's interop usually releases around February https://webkit.org/blog/17320/submit-your-ideas-for-interop-... And yes JPEG XL support is often the most requested feature and the major browsers have responded. Google and Firefox are both willing to take it on but Firefox's biggest concern is with the reference decoder which has some major se…

It took Mozilla two years to decide they were 'neutral', citing a range of vague considerations. It took them another year to say that actually their 'primary concern has long been the increased attack surface of the reference decoder', without pointing out any specific major security flaws, and that they're okay with an implementation in Rust… which had already been proposed by the JXL team many months ago. And let's not even talk about Chrome.

Hopefully they've both finally settled on a reasoning and will stick with it until the end.

Re: PNG in Chrome shows a different image than in Safari or any desktop app

#48

Post by culi »

F3nd0 wrote: post #47
culi wrote: post #42

Earlier quoted context omitted.

Yes exactly. Voting for the 2026 focus areas is happening now btw. The next year's interop usually releases around February https://webkit.org/blog/17320/submit-your-ideas-for-interop-... And yes JPEG XL support is often the most requested feature and the major browsers have responded. Google and Firefox are both willing to take it on but Firefox's biggest concern is with the reference decoder which has some major se…

It took Mozilla two years to decide they were 'neutral', citing a range of vague considerations. It took them another year to say that actually their 'primary concern has long been the increased attack surface of the reference decoder', without pointing out any specific major security flaws, and that they're okay with an implementation in Rust… which had already been proposed by the JXL team many months ago. And let'…

Yeah I guess I wasn't following that closely but I know their previous position was that there wasn't enough benefits to .jxl to justify supporting another raster image standard.

There's been a lot of major changes since then though. Like Apple fully adopting JPEG XL and PDF announcing support as well.

I know many in the industry also think that AV2 might be a huge game changer and wanna wait and see how that ends up before choosing what standards to adopt.

Re: PNG in Chrome shows a different image than in Safari or any desktop app

#49

Post by globnomulous »

hinkley wrote: post #29

> This is an arbitrary picked image, hashed internally and mapped to this page. You will have to see it as long as you in my website. hash: eb46e097… → idx 29/166 What is this nonsense about? I’m on a tablet and over 1/3rd of my screen is basically telling me to go fuck myself?

I don't follow. Could you explain? I also don't see on the website the text you quoted. (Your comment made me giggle though, which I appreciate.)
Post reply on HN