It's fantastic news and I'd like to use it, but is pioneering the new features really necessary while there seems to be so many discrepancies between Safari and other browsers? Shouldn't Apple focus on fixing and closing those gaps first? The website I was working on was tested on version 14.7 and 15+, on Big Sur and Monterey alike. This tweet is about the new, exciting :has() CSS property. “For example, a:has(>img) selects all elements that contain an child.” - from I heard it also from other colleagues and I read it even online in the comments below this tweet.ĭon’t say Safari is always last. As Internet Explorer issues faded away, other issues started to become more apparent in Safari and that’s why Safari is the new IE. Honestly, who cares about IE 11 anymore? Just a very tiny % of people I reckon. Internet Explorer now basically works like Chrome and things got better from both user and developer point of view. How come? How did we get there? Well, on January 15, 2020, Microsoft shifted from the EdgeHTML engine to the Chromium engine. The last time there was an issue it was also Safari related and I said to a colleague that Safari is the new IE. It’s important to check that everything looks great and things are pixel perfect, right? They did cross browser testing and I could fix the majority of the points pretty easily, but then there was a list of Safari-only bugs. I worked on a website recently and I got a feedback from designers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |