alt Hacker NewsProps to the Safari team. They surprised us all when they suddenly shot to the top of interop-2025 this October
Replies
This seems like a bit of a trend with Safari. Around big releases Apple will announce how Safari is the best at X, but other times of the year it gets a lot of flack. I assume this is due to Safari’s more traditional release schedule vs other browsers continuously shipping feature updates.
> They surprised us all when they suddenly shot to the top of interop-2025 this October
Not all of us were surprised; some of us have been watching the Safari team shipping the latest HTML and CSS features for a few years now.
This is not all that surprising. While the Chrome team is out there evangelising things like WebPCIe or whatever, Safari's been shipping features clients actually want, like blurred backgrounds for years before anyone else.
Hm, I know that Safari doesn't support 64bit wasm, which is a very important feature that Chrome and Firefox both have, but this seems to say they have "100% webassembly support".
Fascinating tracker. So we started 2025 with nearly every browser under 80% and ending the year with every browser with >98% interop? That's a lot of amazing work done by a lot of teams. Incredible!
My favorite is finally supporting `arbitrary-subdomain.localhost`. Been a real pain in the neck to add Safari-specific fallbacks for my usage of that.
I wonder if Ladybird has explored running these interop tests yet. Or maybe these are just a subset of WPT?
Safari became the new IE for a while, the amount of problems I've had with Safari CSS animations and SVGs is endless.
It's good they're trying to not make Safari suck as much.
Does it still expand an svg to full size if u omit width and height attributes because u control the size in a parent container? Fuck safari
I didn't realize it was tracked like this, but I have noticed that as of iOS 26, Safari has gotten a huge number of great web features. It has WebGPU of course, but many small things like fixing up missing parts of the OPFS API that make it actually usable now. Now they even have the field-sizing CSS property [0], fixing imo the most glaring ommission from CSS: the inability to make text input boxes grow to fit the input text!
[0]: https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/P...