Safari Ruined My Tuesday
fly.io
Safari Ruined My Tuesday
1–10 of 140 posts
Re: Safari Ruined My Tuesday
#2Re: Safari Ruined My Tuesday
#3Re: Safari Ruined My Tuesday
#4Re: Safari Ruined My Tuesday
#5There is a CSS bug.
CSS bugs are dirt common. It's a miracle that there are as few CSS bugs as there are. However, I remember IE6. IE6 was a total fucking mess. Everything was broken on IE6. It wasn't just a bug, it was a complete support nightmare.
I routinely encounter problems with CSS that reveal maddening differences between Chrome, Firefox, and Safari. That's just for desktop. But it's still way better than dealing with IE6.
Re: Safari Ruined My Tuesday
#6On the one hand, you have Safari whom has a parent company that isn't interested in making it have useful feature parity with the others because it'll then allow escape from their gravy train app store (fully working PWA's, non-compete with rendering engines in iOS). Their lack of keeping up is starting to look a bit like IE6 days.
And on the other, you have Chrome whom has a parent company that claims it wants to improve privacy (FLoC), but to me it is more of a "pulling the ladder up on everyone else" because they have so many other methods to track you (DNS, GA, Android, etc.) that limiting everyone would be disingenuous. Pushing AMP is another example of bullying behavior.
Re: Safari Ruined My Tuesday
#7> It's like living with IE6 again There is a CSS bug. CSS bugs are dirt common. It's a miracle that there are as few CSS bugs as there are. However, I remember IE6. IE6 was a total fucking mess. Everything was broken on IE6. It wasn't just a bug, it was a complete support nightmare. I routinely encounter problems with CSS that reveal maddening differences between Chrome, Firefox, and Safari. That's just for desktop.…
Re: Safari Ruined My Tuesday
#8Google wants everything to be done in the browser, their browser, so they can track everything without cookies to sell ads
Re: Safari Ruined My Tuesday
#9> It's like living with IE6 again There is a CSS bug. CSS bugs are dirt common. It's a miracle that there are as few CSS bugs as there are. However, I remember IE6. IE6 was a total fucking mess. Everything was broken on IE6. It wasn't just a bug, it was a complete support nightmare. I routinely encounter problems with CSS that reveal maddening differences between Chrome, Firefox, and Safari. That's just for desktop.…
Most CSS bugs just make things a bit uglier, rather than completely breaking your entire site.
Re: Safari Ruined My Tuesday
#10I'm trying to figure out which browser is the biggest cancer for the WWW. On the one hand, you have Safari whom has a parent company that isn't interested in making it have useful feature parity with the others because it'll then allow escape from their gravy train app store (fully working PWA's, non-compete with rendering engines in iOS). Their lack of keeping up is starting to look a bit like IE6 days. And on the o…
Tell your manager that you want the web site to support Firefox or Brave or something else, and they'll tell you it's a waste of time.
Tell them that the web site won't work on their MacBook, and it's a four-alarm fire.
In a lot of ways, I wish Safari would deviate even more from Google's "standards" just so that maybe it would pull Big G back to the center some how.