Safari is the new IE6. It's always going to be the weakest / furthest behind major browser.
That role belongs to Chrome, half of their stuff isn't even a Web standard.
Chrome is not the the weakest / furthest behind major browser
Recent improvements to Safari
91–100 of 147 posts
Re: Recent improvements to Safari
#92Derided by whom? From an end user point of view, Safari is the best browser, hands down, on any platform, by a long shot. Performance, smoothness, battery life, mobile integration, password management, the list goes on. I had to support and still know by heart the bugs and idiosyncrasies of IE 5, 6, 7, 8 etc. I have no sympathy for people who say Safari is the new IE.
> From an end user point of view, Safari is the best browser
Maybe if you’ve never used another browser.
Safari is good enough and offers the best battery life. This is all that’s good about it.
The dev tools suck, especially the network tools. The extensions suck. The weird distinction between bookmarks, favorites and reading list makes no sense so I always lose the pages I wanted to keep. On desktop the animations are awful (e.g. when swiping to go to the previous page, it blinks way too much, this is especially visible with Dark Reader because the dark-white transitions will kill your eyes).
I use Firefox on my work laptop and it’s just a better browser. I’ve got no complaints about it.
Re: Recent improvements to Safari
#93Derided by whom? From an end user point of view, Safari is the best browser, hands down, on any platform, by a long shot. Performance, smoothness, battery life, mobile integration, password management, the list goes on. I had to support and still know by heart the bugs and idiosyncrasies of IE 5, 6, 7, 8 etc. I have no sympathy for people who say Safari is the new IE.
by far the worst devtools I've ever had to use. I definitely deride having to pick up a Safari-specific front-end bug for this reason alone
The devtools in Safari are completely unusable to me.
Re: Recent improvements to Safari
#94The addition of push notifications is long awaited, and necessary to take PWA to the next level. It is the single biggest hurdle for me in developing PWAs for iOS. Bring it on!
So bizarre that there are devs think we want webpages with the ability to spam them. Literally the last thing I want from a random website is notification spams and pop up, but woooooo soon I guess I’ll have to get used to pop ups asking me to receive ads from websites all over again.
Let's say you write an email client as a web app. Or a twitter client. Or perhaps an encrypted voice telephony webapp. Of course it is important for them to deliver notifications for those who want to receive them.
This isn't about regular web pages that want to annoy you.
Re: Recent improvements to Safari
#95Overall the progress with Safari in the last has been great, and really shows why it's so important to have competition or even the threat of competition. It's only because of regulatory scrutiny that Apple has been pushed to give the Safari/Webkit the funds they need to make a good browser once again. Still a long way to go to catch up-to Firefox and Chrome but it's heading in the right direction.
>A leaked proposed EU act may force Apple to allow alternate browser rendering engines on iOS. This would give users the choice of which browser and rendering engine to use on their devices.
This has been passed into law. Enforcement should begin in 2024. The UK, Japan & Australia have all proposed similar provisions. Interop 2022 is a few features jointly chosen by the browsers to focus on and work on that year. It's not a good metric for comparing browsers.
>It is worth noting that these changes are still in draft and are early EU proposals with no final decisions yet made. Again it is Final and has been passed into law.
Re: Recent improvements to Safari
#96One very overdue improvement to iOS Safari I noticed: the humble HTML select element. Since the first iPhone, iOS Safari displayed a clunky wheel selector for HTML selects, requiring more taps than necessary to view and select an option from the list. Finally at some point last year they ditched the wheel, replacing it with a simple list (similar to Android), requiring less interaction to select an item. Only took th…
The display used to be 3.5" it make sense back then to have it fullscreen.
Re: Recent improvements to Safari
#97No mention of progressive web apps.
I think push messages in Safari got a mention.
Re: Recent improvements to Safari
#98Earlier quoted context omitted.
It wasn't an inefficiency. It was a way to give users nice scrollable lists with large tap targets on tiny mobile screens.
Super nice to scroll a 150-lines-long list of countries by swiping on a 1-inch-tall target on my huge screen. Even now it's stupid they don't offer keyboard filtering.
Your screen wasn't always huge.
The original iPhone, and many versions after it, was probably 4 times smaller than the current phone.
Even on the current large iPhone screen the dropdown lists (instead of scroll wheels) are usually a pain to navigate because they are often a much smaller target and don't allow mistakes (you mis-click on an item, you have to open the dropdown again)
I agree on keyboard filtering though.
Re: Recent improvements to Safari
#99That's nice to hear. Safari is my main (only, really) desktop browser.
But let's consider this:
"A leaked proposed EU act may force Apple to allow alternate browser rendering engines on iOS... Some experts believe that this would increase competition in the market"
Whoever believes that is not an expert, and hasn't thought it through. Apple's insistence on WebKit is the only thing keeping Chrome from taking over the Web entirely. Once I realized that, I stopped whining about Apple forcing Webkit on everyone in iOS.
Re: Recent improvements to Safari
#100I love how Safari fills in OTP codes from SMS messages automatically. I know you’re not supposed to use them but so many services still do.
I think this is more because Safari has access to that data. Other applications do not, as they are second-class citizens on Mac OS.
No, it’s documented API. It’s either because it doesn’t actually work as documented, or because the other applications’ developers are lazy.
https://developer.apple.com/documentation/security/password_...