Earlier quoted context omitted.
The web is built on the foundation I can use any browser. You are going to break the fundamental promise just to avoid working around a bug?
> The web is built on the foundation I can use any browser. This foundation is provided by browsers and is also broken by browsers. If safari's foundation is broken then safari is the one not fulfilling that fundamental promise, not the websites now broken. So yes, don't use a browser if it doesn't work.
New WebKit features in Safari 15.4
291–300 of 311 posts
Re: New WebKit features in Safari 15.4
#292Earlier quoted context omitted.
Sure, simple websites mostly work in Safari. But we're in 2022, and indeed a lot of companies develop web apps, and not simple websites like 20 years ago. The web itself is an app platform. The only browser preventing it to happen on mobile is Safari. Have a look at the desktop. There, web apps have replaced most native apps long ago.
> The web itself is an app platform. It's not. And frankly will never be. > The only browser preventing it to happen on mobile is Safari. It's not preventing anything > look at the desktop. There, web apps have replaced most native apps long ago. What a strange fantasy world you live in.
Re: New WebKit features in Safari 15.4
#293Earlier quoted context omitted.
I’m sure many of your users would welcome this feature but I’m personally grateful that I don’t get random notifications from websites.
You would not; you must grant a permission to push notifications to the site first.
Re: New WebKit features in Safari 15.4
#294Earlier quoted context omitted.
> decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a workaround) - or if it comes out in iOS 16, then a good chunk of our users will never get the fix I know people like to complain about Safari, but: 1. It’s absolutely common to ask developers for a minimal repro case in a bug report. 2. There are four major Safari releases under 15.x. 3. Apple OS upgr…
"you're holding it wrong" said as "you're too tired". OP's tiredness has nothing at all to do with Apple's abusive policy of forcing Safari on IOS. That's the whole entire problem, not OP not getting enough sleep.
Re: New WebKit features in Safari 15.4
#295Earlier quoted context omitted.
> decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a workaround) - or if it comes out in iOS 16, then a good chunk of our users will never get the fix I know people like to complain about Safari, but: 1. It’s absolutely common to ask developers for a minimal repro case in a bug report. 2. There are four major Safari releases under 15.x. 3. Apple OS upgr…
1. I absolutely agree, and will be making one to get this bug fixed. 2. All of which have different bugs :^) 3. My product's usage data disagrees. We've got plenty of users on old iOS versions - a really big chunk on iOS 14, for example. I want Apple to stop restricting third-party browsers on iOS. MacOS Safari has the same WebGL bugs, but our game's Desktop client uses a WebView under our control & versioning that i…
Re: New WebKit features in Safari 15.4
#296Earlier quoted context omitted.
I really wish Safari would go away and Mozilla would switch to a full featured Chromium with everything enabled (But user-toggle-able). Browser diversity isn't work2 as advertised. It's just Google inventing things that other companies only get a year later, or totally reject. Mozilla needs to start trusting its users to have access to features like Google does, and Apple needs to allow third party browsers without W…
good try google team, but no, go back to work nerfing ublock.
Nor would I be nerfing ublock if I had the choice, browsers are already nerfed way more than enough, and if it were up to me we would have full pluggable network stacks as extensions, with access to raw sockets, so we had a vague chance at ever having a P2P internet that isn't blockchainified.
Re: New WebKit features in Safari 15.4
#297> WebKit added support for lazy-loading images with the loading attribute on the element, providing web developers with an easy way to instruct the browser to defer loading certain images until the user scrolls near them Maybe there's hope that I can then just turn this off on a browser level? I've got gigabit internet at home, and your images popping in on scroll makes it feel like I'm on dial up. Lazy loading image…
Lazy loading images is at best user hostile bandwidth saving The primary use case is to not load images you may not ever see because you may not scroll that far down the page and they don't appear in the viewport. Like any feature, it has to be used correctly by the developer… obviously hero images and other images important to the initial user experience shouldn't be lazy loaded.
That is the "bandwith saving" part. It's user hostile because it is another non-JS privacy leak and because it means that you can no longer open a website to read later when you might not have internet access.
> obviously hero images and other images important to the initial user experience
Hero images are typically the most pointless and irrelevant to the user experience. If you want to save bandwidth then push back against this fad.
Re: New WebKit features in Safari 15.4
#298> New support for BroadcastChannel allows tabs, windows, iframes, and Workers from an origin to send messages to each other. This enables experiences like syncing login state for a site across multiple tabs. This is SUPER nice... there are other hacks like IndexedDB or localStorage but this is way better! But the frustrating part her is that we're excited about Webkit finally starting to catch up. Chrome is just perp…
I think this means SharedWorkers are not too far behind. Pretty sure I saw a issue tracker indicating maybe SharedWorkers had been restored in a nightly build?
Re: New WebKit features in Safari 15.4
#299Earlier quoted context omitted.
I’m surprised by all the heat around the push notifications API. Is it really going to mean that much to web apps? I’m assuming it will work pretty much like push notifications on desktop, which is an awful UX.
It would mean a great deal to all sorts of web apps! To provide just one example, I released a turn-based word game as a PWA two years ago. With no option for native push notifications on iOS, I decided to email players to notify them each time it was their turn in a game. Despite my domain having full support for DKIM, SPF, and DMARC, the usual problems of email were still a huge pain: Some domains (I'm looking at y…
Re: New WebKit features in Safari 15.4
#300Earlier quoted context omitted.
Safari on my iPhone is basically unusable. Refreshes the page constantly; swipe back a page and it refreshes; scroll down long enough and it refreshes. Then there's Reddit - crashes constantly, literally will not load comments. It does this with and without extensions.
Sounds like you’re on an old phone? I did have RAM issues on the 11 Pro that unloaded every app as soon as I opened the camera, but otherwise tabs did not unload that often. Reddit is its shitshow and I ended up installing Apollo. This is not Safari’s fault.