Safari (desktop and mobile) also has tracker blocking built in. "Prevent cross-site tracking" and "Hide IP address from trackers" are two settings it has; I think the first is checked by default, I don't remember about the other.
In the DevTools network pane, it shows requests to known trackers, like Google Tag Manager, being blocked.
Try using Amazon in Safari sometime (in Lockdown Mode, no less): non-stop ads (some which flash), sponsored results dominating the first page of search, random Dufus pop-ups forcing AI. You can hide "distracting" elements but they just appear again later. Safari is not a user-friendly browser.
Safari is my default browser. I don't know what "Dufus" means, I don't recall any A.I. references. On Amazon, it's all first-party stuff, what browser blocks that natively? It seems like you're comparing using Safari without an ad blocker to a different browser with an ad blocker.
I know the most popular ad blocking extensions don't make a Safari version but there are ad blockers for Safari.
I don't get any of that in Safari or any other browser. "Rufus" is just a button in the main navigation, between "All" and "Same-day delivery" that I ignore. On individual product pages, there's "Ask Rufus" stuff in a couple of pages but it's no worse than other content I scroll past and seems just like previous features that didn't have a named AI identity.
Yes, the tabs in a tabs pattern should be keyboard navigated using arrow keys (ironically not the Tab key).
Also, the summary for the currently open details element will have the wrong state, 'expanded' instead of 'selected'. And while a set of details can now have a maximum of one open at a time, you can't ensure exactly one is always open (without JavaScript) as the tabs pattern requires.
That's not correct. There is no aria-open attribute and the summary implicitly has the correct ARIA state, aria-expanded, indicating that its details element is either expanded or collapsed.
There have been bugs in its implementation, particularly in Safari and differing between mobile and desktop Safari.
Yes, Google started revealing the contents of <details> a few years ago, long after the element was supported in all browsers. Firefox added support earlier this year and Safari just added it.
Supporting the behavior was related to changing the user agent CSS when they're closed and the other browsers implemented it and hidden=until-found at the same time.
Especially when you don't approach it that way; they made an HTML game in desktop Chrome then worked on getting it to work in various mobile browsers, including quite old ones.
The article gets to the right conclusion, develop mobile first. I'd put it more generally as develop for the most constrained devices you intend to support. If they had done so, it would have saved a lot of time (some of their expectations about APIs still would not have been met).
When I pointed out some bugs on Microsoft's docs they just basically replied "hurry up and fix them then!" which annoyed me at first, but they actually poked me until I stopped being lazy and submitted a PR, wherein I actually learned some new things.
