Live data from Hacker News

New WebKit features in Safari 15.4

webkit.org

81–90 of 311 posts

Re: New WebKit features in Safari 15.4

#81
post #57

> 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.

Re: New WebKit features in Safari 15.4

#82
post #65

Earlier quoted context omitted.

That would annoy me, too. Maybe they could have it only work for when you Add to Homescreen as a progressive web app, then it would be more opt-in.

This is actually the perfect compromise that I haven’t even thought of until you’ve mentioned it. Up until now, I was opposed to webkit push notifications for the same reason as the grandparent comment. Thank you for your comment.

You're welcome! Yeah, I didn't even know that they could segregate it based on whether it was going through the Add to Homescreen option, but learned of it through the article:

> Web App Manifest improvements include ensuring the browser always fetches the manifest file during page load instead of when the user chooses to “Add to Home Screen” from the Share menu.

Re: New WebKit features in Safari 15.4

#84
post #57

> 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…

The idea is that the browser, which is aware of your bandwidth, will disable this for you. But for a user on a limited bandwidth connection it’ll implement it. In other words the lazy attribute is a suggestion, not an instruction.

The experience you describe is with JavaScript lazy loaders which don’t have this awareness.

Re: New WebKit features in Safari 15.4

#85
post #52

Web MIDI? Still surprised that's missing on Apple.

I believe Apple and Mozilla’s position is it can’t be done in a privacy preserving way as currently specified.

WebMIDI support in Firefox is almost complete. https://bugzilla.mozilla.org/show_bug.cgi?id=836897

Re: New WebKit features in Safari 15.4

#86
post #57

> 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…

Unfortunately if you want to rank these days you have to implement these kind of things, or Google marks you site down as having poor performance. At least with a standard attribute there is now a chance for a simple browser setting to turn the behaviour on/off/auto depending on connection type/etc.. unlike all of the various javascript solutions.

Re: New WebKit features in Safari 15.4

#87

Earlier quoted context omitted.

Are there any comparisons of where content blockers fail and ublock origin is better for a casual user?

Somebody correct me if I'm wrong but last time I checked I couldn't find any content blocker for MacOS Safari that would block pre-roll Youtube ads whereas uBlock Origin in Chrome, Firefox, etc. does not have this problem.

I develop an ad blocker - Magic Lasso Adblock [1] for Safari that flawlessly and completely blocks all ads in YouTube. It works across iPhone, iPad and Mac. So it can be done and the experience works when implemented correctly.

[1] https://www.magiclasso.co/

Re: New WebKit features in Safari 15.4

#88
post #73

Earlier quoted context omitted.

If you don’t have gigabit internet (i.e. most people), then it’s not so user hostile.

In my experience it's more user hostile the worse your connection, because they have to sit and watch the images load for an even longer amount of time than I do, whereas it could have kept loading for them ahead of time. Where without lazy loading they could normally get up and get a cup of coffee and come back, you are now actively wasting their time as they scroll.

If the person is viewing a gallery website, perhaps, but most websites are centered around textual content, which would be available much faster with lazy loading of images, thus the user on poor connection would actually get the _useful_ part of a website much faster.

Re: New WebKit features in Safari 15.4

#89
post #57

> 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…

[deleted]

Re: New WebKit features in Safari 15.4

#90

Earlier quoted context omitted.

I thought I read [0] that there will be experimental support for push notifications in 15.4. Perhaps keep any eye on advanced safari settings when it comes out?. At least there appears to be progress, and you may be able test it. [0] eg, https://www.macworld.com/article/610673/ios-15-4-safari-push...

It’s in there but but not enabled by default, meaning it’s still in beta. It’ll probably be officially announced at Apple’s World Wide Developers Conference in June.

If we can enable it for our own purposes then that's big. Doesn't need to be on by default.
Post reply on HN