Comment by dangus
20 days ago
All I know is the other two browser major engines work a lot better in practice than WebKit.
I don’t really know or care as an end user if WebKit represents browser choice. The fact is they Apple isn’t putting enough effort in to making their browser engine “just work” with popular websites.
If it was a requirement in iOS and a default in macOS nobody would choose it by choice. It would be dead as a doornail if it competed in a free market.
In my experience a comparatively broke Mozilla Foundation makes a better browser experience than the most profitable consumer electronics company in the world. Apple needs to do better.
Why is it on apple to make teams work for their web browser and not the other way around?
Because it’s not just Teams that’s broken, it’s a solid percentage of the websites I visit.
Apple can’t blame developers for their browser’s inconsistency.
Firefox has 1/10th of Apple’s market share and that browser is clearly more compatible with websites in my experience.
Whenever I have some kind of rendering issue or functionality glitch in Safari I switch to Firefox and it works fine.
Like, dear lord safari can’t even implement the back button normally. The behavior is terrible. It’s like you see a static screenshot of the precious page and everything is frozen for a second, and then if you’re lucky it unfreezes and at worst your scroll position gets messed up, or you’re unlucky and the entire page reloads.