4 ms·

No, but Safari routinely causes many problems that seem utterly basic for Firefox/Chrome.

by rashil2000 5y ago

rimliu 5y ago
Because you develop on Chrome, and only occasionally test on Safari. Try the other way around and see which one is buggy.
- realusername 5y ago
  I develop on Firefox, everything is fine on Chrome but there's always some bugs in Safari.
- mmis1000 5y ago
  Like safari ignores layer ordering during scroll? Which is something that god damn ie6 15 years ago can do properly? Is z-index even a new feature whatever? The safari basically can't even guarantee it can do other browser done properly many years ago (or you can say it is buggy even you only use css 2 feature).
- danaris 5y ago
  I think this really needs to be emphasized strongly. I develop primarily on Safari, and only occasionally test on Chrome (for my hobby side project), and occasionally I run into instances where Chrome differs. To me, those look like Chrome bugs because Safari is my "default". If you're using Chrome (or Firefox, which, in my recent experience, tries specifically to be compatible with Chrome because Chrome is the overwhelming default for people like IE was) primarily, and expecting Safari to exactly match its behavior, of course you'll run into various cases where Safari appears buggy. But to use that to claim that Safari is "the new IE6" is just ludicrous. I don't know how old other people in this thread are—maybe those making the comparison to Safari weren't actually around for the IE era, or maybe it's just been so long you've forgotten how bad it really was—but I was actually doing some web development back when IE6 and even IE4 were common. They were an absolute nightmare. I don't recall the precise details at this late date, but there were fairly basic HTML tags they didn't implement, and others they implemented completely differently. Javascript features were all over the map. That realusername has to dig up four fairly esoteric edge-case issues to show that Safari is "total nonsense", and then have HatchedLake point out that at least two of those aren't even current, is ample proof that it's the comparison of IE to Safari that's total nonsense.
  - realusername 5y ago
    > , but there were fairly basic HTML tags they didn't implement, and others they implemented completely differently. Javascript features were all over the map. For the tags I do agree but for the Javascript I have a good bunch of pollyfills just for Safari in place. > That realusername has to dig up four fairly esoteric edge-case issues to show that Safari is "total nonsense", and then have HatchedLake point out that at least two of those aren't even current, is ample proof that it's the comparison of IE to Safari that's total nonsense. All of those issues are current and very much not fixed. Yeah they are very old and have been there for almost 10 years I do agree, but it's still broken now, even after 10 years.
- rashil2000 5y ago
  Why does this matter so much? Our team purposefully decided to use a really well known component library (Material UI React) so that it automatically takes care of browser inconsistencies. But no, I still find myself and my team scratching our heads writing a ton of Safari-specific CSS just to ensure it works on par with Firefox.

No, but Safari routinely causes many problems that seem utterly basic for Firefox/Chrome.

Because you develop on Chrome, and only occasionally test on Safari. Try the other way around and see which one is buggy.

realusername 5y ago
I develop on Firefox, everything is fine on Chrome but there's always some bugs in Safari.
mmis1000 5y ago
Like safari ignores layer ordering during scroll? Which is something that god damn ie6 15 years ago can do properly? Is z-index even a new feature whatever? The safari basically can't even guarantee it can do other browser done properly many years ago (or you can say it is buggy even you only use css 2 feature).
danaris 5y ago
I think this really needs to be emphasized strongly. I develop primarily on Safari, and only occasionally test on Chrome (for my hobby side project), and occasionally I run into instances where Chrome differs. To me, those look like Chrome bugs because Safari is my "default". If you're using Chrome (or Firefox, which, in my recent experience, tries specifically to be compatible with Chrome because Chrome is the overwhelming default for people like IE was) primarily, and expecting Safari to exactly match its behavior, of course you'll run into various cases where Safari appears buggy. But to use that to claim that Safari is "the new IE6" is just ludicrous. I don't know how old other people in this thread are—maybe those making the comparison to Safari weren't actually around for the IE era, or maybe it's just been so long you've forgotten how bad it really was—but I was actually doing some web development back when IE6 and even IE4 were common. They were an absolute nightmare. I don't recall the precise details at this late date, but there were fairly basic HTML tags they didn't implement, and others they implemented completely differently. Javascript features were all over the map. That realusername has to dig up four fairly esoteric edge-case issues to show that Safari is "total nonsense", and then have HatchedLake point out that at least two of those aren't even current, is ample proof that it's the comparison of IE to Safari that's total nonsense.
- realusername 5y ago
  > , but there were fairly basic HTML tags they didn't implement, and others they implemented completely differently. Javascript features were all over the map. For the tags I do agree but for the Javascript I have a good bunch of pollyfills just for Safari in place. > That realusername has to dig up four fairly esoteric edge-case issues to show that Safari is "total nonsense", and then have HatchedLake point out that at least two of those aren't even current, is ample proof that it's the comparison of IE to Safari that's total nonsense. All of those issues are current and very much not fixed. Yeah they are very old and have been there for almost 10 years I do agree, but it's still broken now, even after 10 years.
rashil2000 5y ago
Why does this matter so much? Our team purposefully decided to use a really well known component library (Material UI React) so that it automatically takes care of browser inconsistencies. But no, I still find myself and my team scratching our heads writing a ton of Safari-specific CSS just to ensure it works on par with Firefox.