3 ms·

If you think Safari is the new IE, you have definitely forgotten (or not experienced) how bad things were with IE6. They didn’t just have a few bugs in their b

by mikl 4y ago

If you think Safari is the new IE, you have definitely forgotten (or not experienced) how bad things were with IE6. They didn’t just have a few bugs in their browser implementation or were slow to implement new features. Basic, crucial CSS features were broken. Microsoft didn’t add any new features to the browser about a decade, basically holding the entire web back to the standards of circa year 2001 until it was finally safe to drop support for it almost a decade later. And furthermore, Microsoft weren’t pushing users to upgrade to the latest version, so we had to support older versions of IE long after their replacements were released. I understand wishing that Safari would be better, but luckily the Safari team is much more on the ball than the IE team ever was.

mmis1000 4y ago
A few…? It's not my experience as a web developer. It's 'a lot' at best. And not only in js, but also in css or literal anywhere you might interact to. It always requires a few workaround when I finished the page in other browser. Firefox or Chrome, in the other end. If your page works on one of them, it will pretty much just work on the other. Safari is probably 50% of my bug ticket, almost equals to every others sums together. Write a page for safari really reminds me the age IE is still a thing.
- culi 4y ago
  Interesting. I've run into issues with the way Safari handles transparency values, but don't actually come across many other Safari specific issues these days. Safari has been pouring a lot of effort into improving their web compatibility recently and I feel like it's already making a difference I'd be very curious to hear some common issues you have to deal with
PpEY4fu85hkQpn 4y ago
I agree. The people who call Safari the new IE probably don't know what zoom: 1; does and how fundamentally broken so many basic things were in IE6.
makeitdouble 4y ago
You have a point, yet I feel the situation isn't as bright as you make it look. I think Safari isn't broken in the ways IE was, because IE always had comptetitors running along it and pushing the enveloppe where Microsoft was pulling the brakes. Firefox and later Chrome were handicaped in adoption, yet had little to no limitations on the features they wanted to add. In comparison no other browser can run with the same privileges as Safari on the phone, while the iPhone is a dominant platform. So there just isn't the same space to innovate in a profitable way. The only company who can afford pushing the envelope is Google, and at this point their only real competitor is Firefox, that they basically pay to keep alive. They also have little incentve to really push the web as it doesn't impact their bottom line (native app ads also go in their pockets afterall)
sccxy 4y ago
Safari IS new IE. I have submitted 10s of webkit bugs and most of them will never get fixed. New bugs randomly appear in every OS update. 5 year old cheap android device can handle complex webpages really well, but my 1500 eur brand new iPhone runs out of memory. iOS Safari is really buggy. I work with online maps.

by mikl 4y ago

mmis1000 4y ago

A few…? It's not my experience as a web developer. It's 'a lot' at best. And not only in js, but also in css or literal anywhere you might interact to. It always requires a few workaround when I finished the page in other browser. Firefox or Chrome, in the other end. If your page works on one of them, it will pretty much just work on the other. Safari is probably 50% of my bug ticket, almost equals to every others sums together. Write a page for safari really reminds me the age IE is still a thing.

culi 4y ago
Interesting. I've run into issues with the way Safari handles transparency values, but don't actually come across many other Safari specific issues these days. Safari has been pouring a lot of effort into improving their web compatibility recently and I feel like it's already making a difference I'd be very curious to hear some common issues you have to deal with

PpEY4fu85hkQpn 4y ago

I agree. The people who call Safari the new IE probably don't know what zoom: 1; does and how fundamentally broken so many basic things were in IE6.

makeitdouble 4y ago

You have a point, yet I feel the situation isn't as bright as you make it look. I think Safari isn't broken in the ways IE was, because IE always had comptetitors running along it and pushing the enveloppe where Microsoft was pulling the brakes. Firefox and later Chrome were handicaped in adoption, yet had little to no limitations on the features they wanted to add. In comparison no other browser can run with the same privileges as Safari on the phone, while the iPhone is a dominant platform. So there just isn't the same space to innovate in a profitable way. The only company who can afford pushing the envelope is Google, and at this point their only real competitor is Firefox, that they basically pay to keep alive. They also have little incentve to really push the web as it doesn't impact their bottom line (native app ads also go in their pockets afterall)

sccxy 4y ago

Safari IS new IE. I have submitted 10s of webkit bugs and most of them will never get fixed. New bugs randomly appear in every OS update. 5 year old cheap android device can handle complex webpages really well, but my 1500 eur brand new iPhone runs out of memory. iOS Safari is really buggy. I work with online maps.