4 ms·

Fixing any issue specific on Safari is a whole challenge on another level. Hope you had an easy time debugging issues on Safari.

PaulHoule 4y ago
At work we've never had one that was that bad. In one cases it was third-party cookie issues that affected Safari before everyone else. Personally Safari is the reason why some of my image-based sites still use JPG in parallel with WEBP. I think they fixed it just recently, but if you have an older mac (i do) Apple couldn't be bothered to include a WEBP codec with the OS. Firefox, Chrome and every other browser for mac supports WEBP but not Safari. I think they resolved this in the last month, but I think for better or first Apple wants to roll out new SIMD instructions in their libraries much faster than Microsoft does. So at some point your CPU is too old. Of course the flip side to that in the Windows World is that people are stuck using a 10 year old instruction set. Intel doesn't seem to get it that by not supporting the latest AVX in their latest chips that people just "don't use AVX". If the latest SIMD instructions were widely supported you'd have a reason to buy a new computer, but when they aren't Intel has lackluster sales and wonders why.
- warrenm 4y ago
  Honestly, I thought pretty much everyone had moved to PNG from JPG by now
- sachinjain 4y ago
  I have had a very nasty bug that I debugged in Safari. Chrome & Firefox supports redirects to http when the site is on localhost or 127.x.x.x but Safari doesn't and throws a Mixed content warning error. Another one was similar when redirect chain got broken because of an intermediate redirect (https -> https -> http -> https) I guess Chrome & Firefox automatically upgrades the protocol now but Safari doesn't and it broke the chain and it was also not showing the broken redirected chain in the Safari developer tool.

PaulHoule 4y ago

At work we've never had one that was that bad. In one cases it was third-party cookie issues that affected Safari before everyone else. Personally Safari is the reason why some of my image-based sites still use JPG in parallel with WEBP. I think they fixed it just recently, but if you have an older mac (i do) Apple couldn't be bothered to include a WEBP codec with the OS. Firefox, Chrome and every other browser for mac supports WEBP but not Safari. I think they resolved this in the last month, but I think for better or first Apple wants to roll out new SIMD instructions in their libraries much faster than Microsoft does. So at some point your CPU is too old. Of course the flip side to that in the Windows World is that people are stuck using a 10 year old instruction set. Intel doesn't seem to get it that by not supporting the latest AVX in their latest chips that people just "don't use AVX". If the latest SIMD instructions were widely supported you'd have a reason to buy a new computer, but when they aren't Intel has lackluster sales and wonders why.

warrenm 4y ago
Honestly, I thought pretty much everyone had moved to PNG from JPG by now
sachinjain 4y ago
I have had a very nasty bug that I debugged in Safari. Chrome & Firefox supports redirects to http when the site is on localhost or 127.x.x.x but Safari doesn't and throws a Mixed content warning error. Another one was similar when redirect chain got broken because of an intermediate redirect (https -> https -> http -> https) I guess Chrome & Firefox automatically upgrades the protocol now but Safari doesn't and it broke the chain and it was also not showing the broken redirected chain in the Safari developer tool.