> I have heard designer friends say that Firefox is the new IE for them > Safari seems to be a designer-favourite with a very strong focus on things designers

> I have heard designer friends say that Firefox is the new IE for them > Safari seems to be a designer-favourite with a very strong focus on things designers need. I have the completely different experience. If anything Safari is the new IE6 here. It has bizarre JavaScript behaviour mismatches from other browsers because it doesn't conform to the standard and does its own thing instead. However, some of these problems are only present on iOS/macOS because they're related to the underlying libraries used/provided by those operating systems. It also has "edge-case" (I'd call them quite common, actually) rendering issues that haven't been fixed for at least a few years now (their flexbox model is still broken). Sometimes they even don't really treat these as bugs either but instead assume a high ground and claim their way is the best way. Sounds familiar? Both Chrome and Firefox have some issues where things don't work properly, or deviate from the standard, and these are treated as bugs, and there's much fewer of those. In my experience Firefox in general has more of these issues than Chrome and it usually requires a bit of added fluff to get it to work as the documentation claims it should work, but they're usually fixed quickly since there's usually already a bug report for them. Chrome on the other hand has some subtle issues with rendering, and ironically a lot of them seem to be with the table model—which you'd think should be robust given its age, and some of them have not been fixed for ages, simply because people are moving away from the table model and interest in these bugs is dropping. The table model has technical design issues to begin with, anyway.