- leading on the Interop 2022 dashboard results [1]
- posting the best Speedometer score on the Mac [1]
- changing their pace of innovation and releases to deliver newer API features in a quicker manner
I'm shocked you'd choose Brave over this, whose security history and business model is very, very questionable.
https://giorgiocalderolla.com/wipr-faq.html#what-is-wipr-ext...
Naturally, Safari Extensions seem to more frequently cost money since Apple's developers have to pay for Mac hardware and developer accounts. But to say that Safari doesn't have good enough extension capability from a technological level doesn't seem to be true anymore.
On my Mac Safari is my default browser due to the battery efficiency and OS integration (e.g., SMS code integration), but I do sometimes use Firefox/Chrome for specific websites where needed, something like 5% of the time.
1Blocker - a well known 'traditional' safari content-blocker - does this for example, to provide ad blocking on sites like YouTube.
Open Source ad-blocker with silly name but its great.
Vinegar
Native video player on youtube, also means no ads.
Hush
Hides cookie consent dialogs (this sometimes break some sites, thanks EU)
Are browsers that don't use Webkit as an engine (just their own skin on top of it) allowed on MacOS? Or is that just iOS?
It would be nice for all users to get access to these new APIs via a simple app update. This would allow developers to actually start using them within days/months rather than years.
Right now I'm having to debug an obscure issue with Safari and Mojave.
In my experience, coupling the browser with the OS version has been nothing but problems.
Edit: Sorry, missed the part about the "mobile" safari. You're right, I don't think it's available for mobile.
Fortunately the cutoff I've chosen for my current project isn't that bad - 15.4. It means some iPhone users won't be able to use it. Eventually I'll feel OK about requiring 16.4. But I second the request for being able to install a new version without upgrading the whole OS.
Now if we could get periodic background sync api, and vibration api, that would be perfect.
A next major step is inclusion into the app store, but until then this is a major win for PWA.
New wake lock API does not work in PWA, only works in Safari...
Apple is making sure that nobody will use PWAs.
Ah yes. The amount of random APIs that are an absolute necessity for something to be called the true PWA just keeps growing with every release.
https://developer.apple.com/documentation/safari-release-not...
The SaaS grifters will metastasize, multiply and deliver their snake oil as they did to Android now onto iOS users only to degrade the platform further.
(1) For this to work at all, users will need to have added the app to their Home Screen.
(2) Because they "work exactly like notifications from other apps", you can easily control when they're able to interrupt you, and also easily mute abusers.
"To pay your phone bill, please add the T-Mobile web app to your Home Screen."
"To read the rest of the article, please add the News web app to your Home Screen."
Relatively easy to work with, though I hope their OS integration will add support for more native iOS notification features like actions.
If you wanna try out native push notifications it's pretty fast to try out: https://alerty.dev
Edit: on the account page, it says “You're currently on the free plan.” But I can’t do anything with notifications.
I hope Safari iOS adds support for actions and shortcut workflows when clicking a notification.
Because that title is reserved for a certain behemoth that enjoys the same popularity as IE6 once had and which IMO is probably more dangerous to the free web than IE6 was when EU reacted.
Like styling scroll bars in FireFox. But more often it feels like Safari is the special needs browser.
Sometimes it's because it lags on features. Sometimes it implements a spec differently. Maybe it's the websocket bug of 2021/2022 that took forever to fix(was it?!) because their weird update cycles.
It all adds up.
Does Safari lack support for some actual standards? Sure. No browser is "feature complete". The difference is, a good chunk of what people complain about, are draft features, made available in Chrome because Google's whole business model is "put everything in a browser, and track the bajeezus out of it".
But IE6 was not spyware, it was a browser that was maddening to use, and purposely anti standards. That title, currently, is theirs alone.
* It is really no contest - Chrome is king. But even Google's little things - G-Fonts loads JS to track users on websites, and Android SDK installs an updater that also spawns nameless DLLs that run in the background and regularly send info home, would be impressive for any other spyware app...
When you "install" an PWA, you can only keep it on the Home Screen, while native apps can be removed from Home Screen (not uninstalled) and only shown in the library
Web Push is fantastic for developing useful applications without paying the apple tax, which necessarily results in the garbage-tier free apps dominating the App Store today (Want to do anything at all? Watch an ad every minute. Want functionality that's not the absolute bare minimum? Pay $5/month forever.)
I wonder if you realize that these days Firefox is more often than not on Safari's side when it comes to all the things you've listed.
It's even funnier that they shipped fullscreen api to iPad and intentionally ignore iPhone without a reason.
Right now I take people to a secret URL with long generated token so the web app will also have it and be able to correlate the two. Yes I can have the user re-sign-in with credentials, or webauthn, but seems overkill.
Also can Apple add some sort of thing like Chrome has “beforeinstallprompt” to actually show an install promopt?
Apple's philosophy is that it needs to be on the home screen, and that popups prompting users to install the app were a mistake (many people will allow notifications and app installs just to dismiss prompts). Making people do a song and dance should reduce the potential for "your grandparents" accumulating an infinity gauntlet of spam notification PWAs.
Obnoxious autoplaying video is a scourge.
Passes feature detection but does not work in home screen.
Just like in IE you need to add some extra if’s for Safari version and environment detection.
Edit: Looks like someone may have already reported it 3 years ago: https://bugs.webkit.org/show_bug.cgi?id=210061
> The space for the saved accounts is there, yet the text is empty. There's nothing to select
Sure sounds like what I'm seeing, except instead of being intermittent it's always like that.
Really excited to see some cool custom form inputs, and for those will inevitably say "use the native form elements, dont make your own!" I agree when that's an option, but often times you do want custom form inputs (i.e. a video uploader form element that allows you to define crops / cuts / etc). This will open up the options for things like that, and will result in some great custom experiences that are also accessible.
Interesting that they still don't support Media Source Extensions on iOS but are adding WebCodecs support. I keep hoping Safari will add MSE, as I'd like to support both live and historical content with one API on all browsers. WebRTC doesn't seem suitable for historical. Chrome and Firefox don't support HLS. Now WebCodecs seems the most likely option, by Firefox adding support. Fingers crossed that will happen... I haven't really played with WebCodecs but it seems nice in concept.
For example, in a feed of post where one post has a 'sponsored' text element, the :has() selector could be used to easily target the full sponsored post while leaving organic posts untouched.
