I think I kind of hate lazy loading

https://shkspr.mobi/blog/2023/09/i-think-i-kind-of-hate-lazy-loading/

by edent • 3 years ago

136 173 3 years ago

ttfkam4• 3 years ago

It's curious that some folks hate the side effects of insufficient infrastructure while missing that the lack of modern infrastructure is the root problem.

It is entirely possible to get a cell signal on a train, even in tunnels. We as a society just choose not to build out the necessary infrastructure.

gonzo41• 3 years ago

Europe has the benefit of having had a lot of roads created by the Romans. Infrastructure takes time.

dylan604• 3 years ago

But it burns in a day?

NotYourLawyer• 3 years ago

Adding physical networking infrastructure to all the trains and everything else is a much bigger job than adding a setting to a browser that lets the user opt out of lazy loading.

mvdtnz• 3 years ago

As a software developer I have very little control over rail infrastructure. However I have almost total control over the HTML attributes I emit.

ttfkam4• 3 years ago

As a user, I have very little control over 99.999% of all sites' infrastructures. We were talking about lazy loading on a train. Most users have no control over the HTML attributes they receive.

As software developers make up a vanishingly small amount of all users on trains, it seems prudent to highlight their collective experience, not the portion of a one-off that you can control as an individual contributor.

I'm well aware that you or I as individuals have very little control over public transit infrastructure. It's a shame we cannot team up as a group to solve these issues rather than fixate on our experiences solely through a personal lens.

vorpalhex• 3 years ago

Right, because it's expensive and difficult and would make the train cost more.

You could have truly wireless electricity power your phone and never have to recharge. You just need to invest in more infrastructure.

ttfkam4• 3 years ago

Right, because it's expensive and difficult and would make the train cost more.

That you (and others) think network connectivity is anything higher than a rounding error in terms of rail infrastructure costs is likely part of the problem.

tekla• 3 years ago

It is the web developers choice to decide whether or not to deal with bad/poor internet connections. Most do not.

Lazy loading makes it impossible to do anything to manage a poor connection.

tentacleuno• 3 years ago

Seems hard not to these days, especially with service workers which can cache resources for offline use.

vhcr2• 3 years ago

In this case it's also the choice of the user, they could choose to ignore the lazy loading tags (I know OP mentions their browser doesn't supports it, but they could choose another browser)

syndicatedjelly2• 3 years ago

Lazy loading makes it impossible to do anything to manage a poor connection.

This was the exact problem lazy loading was supposed to solve

Vanit• 3 years ago

Ah, it's the users who are wrong!

In all seriousness, as engineers we of course can't assume the happy path is common, and to ensure good UX more often than not we need to account for these cases.

ttfkam4• 3 years ago

I'm not sure how you possibly got that reading from what I wrote.

I'm am discussing a solution rather than a series of ephemeral and incomplete fixes. Not that developers can solve public transit issues but that society at large is the only one that can truly solve these issues.

The users are not wrong in my assertion nor do I think disabling lazy loading is the solution. Disabling lazy loading is an ephemeral and incomplete fix that helps some scenarios while degrading the experience in other scenarios.

The solution is improved infrastructure. I don't see why this position is controversial.

spaceprison• 3 years ago

So: developers can't change the way society has chosen to prioritize infrastructure, Poor user experience is the result of this societal failure, thus there is nothing that can be done to improve user experience?

It seems more likely that the expectation that users must have consistent connectivity to load (and keep loaded) the most fundamental aspects of a website (images and text) is a poor assumption and the hubris to leave this type of assumption unchecked the actual root problem.

alpaca128• 3 years ago

Software is easier to adapt than everything else and users don't care why your website doesn't work properly.

Building a website with the assumption that the user will have a perfect internet connection is like writing an application without error handling. When something goes wrong you can't just blame reality for being imperfect.

forgotmypw173• 3 years ago

Lazy loading breaks a lot of functionality.

For example, I open a webpage and then go offline. Later, I scroll down, but the content is missing.

Another time, I open a webpage and save it. But most of the content is not saved, because it has not been loaded.

The network activity is actually higher for a page with lazy-loading elements.

All-around, it does not make any sense to me, personally.

hn_throwaway_993• 3 years ago

Both of these seem like uncommon edge cases. I can't remember the last time I actually "saved a webpage" - I think in my using the web for nearly the past 30 years that functionality hardly ever worked well in the first place. I do use print-to-PDF fairly often, but honestly don't know how lazy load works in that scenario. If you choose to print all pages and it doesn't include lazy loaded images, I'd just consider that a bug.

forgotmypw173• 3 years ago

For you, they are uncommon edge cases. For me, they are everyday usage.

rightbyte• 3 years ago

Given how much link rot there is I would have wanted all my non-porn non-bank website visits to be saved to some encrypted folder, in some way.

Especially since Google got so bad you can't refind webpages you know exist.

lstamour2• 3 years ago

It feels like this is something the browser can solve by working towards these edge cases as bugs to fix. Especially saving the webpage with lazy loading. I've encountered similar issues when using iOS Share menu to convert a webpage to a PDF or Reader PDF, where sometimes you have to scroll the webpage first before it exports correctly. These are bugs that web browsers need to fix. Similarly, there should be some kind of warning or progress bar if you have downloads in progress but want to go to airplane mode. It could be optional, but like when you close your browser and downloads are still running, it could ask if you want to go offline after downloads finish, for example.

ponderings3• 3 years ago

could hold down the space bar until you are at the end, then save.

forgotmypw173• 3 years ago

That is a great idea, but actually does not work, because the browser redownloads the page from scratch when I save. Also, it has to be done for every page, which I would have to remember to do each time.

JohnFen2• 3 years ago

I open a webpage and then go offline. Later, I scroll down, but the content is missing.

This bites me often, too. It's always infuriating.

hn_throwaway_993• 3 years ago

A weird complaint if you ask me.

Browsers and developers should try to do their best with limited resources. So it most cases that means making predictions about user behavior. Sometimes that means preloading content (e.g. if you're on a landing page, preloading content from the next likely page will make the it feel much more performant) and sometimes lazy loading to not waste resources if a user isn't going to see content in the first place.

But of course there will be "bad branch predictions" sometimes. I think "having a page load before I get into the tunnel but not scroll down enough to have content load before I lose Internet connection" certainly seems like a case that it's fair not to optimize for.

WillPostForFood4• 3 years ago

Instead of all the complexity and code and branch predication, how about just send the page and the images? If lazy loading is super important, the browser can lazy load and render off screen. Don't make thousands of solutions for thousands of platforms on the server side.

quickthrower22• 3 years ago

I agree but changing the world to that would be quite a fuss. But if that was already where we are at it would be better. But the JS as an Operating System per site ship has sailed.

hn_throwaway_993• 3 years ago

I don't understand your comment at all.

Before the loading attribute on img, developers did have lots of custom solutions for lazy loading. A major point of lazy loading is to save resources on the server that would be wasted when serving an image that is never seen.

quickthrower22• 3 years ago

I agree. A simple way to solve it is to make the article readable without images. Good old alt tags! A data science heavy article may not benefit. But a dozen words can paint a picture.

xnx2• 3 years ago

I generally dislike lazy loading. My time is almost always worth more than data transfer costs, so I'd much rather load up a bunch of stuff I might not see so that in the office chance I fast scroll down the page I don't have to wait for anything.

hunter2_7• 3 years ago

You're thinking of your own costs; the developer is more likely thinking of their own than yours.

duxup• 3 years ago

As a web dev… I honestly have never thought of it that way in terms of cost.

I would rather a user see the whole page, consume all the content, it’s not a big cost.

viraptor3• 3 years ago

As a developer adding lazy loading... nah. The motivation is more about prioritising resources. I want some images to load after everything else to free up the bandwidth for now critical resources. If I had the option of "when the connection is idle for 2s", instead of the current implementation of "lazy", I'd use that.

I'm sure there are some other services which are more image heavy and will save some money this way, but it's not the only reason.

nicbou2• 3 years ago

I live in Germany and so do most of my users, so I take the spotty internet rather seriously. There are lots of holes in the coverage even in the capital. Then there is the underground.

However loading the images early wastes bandwidth, and it hurts SEO. In my case the user can live without those images, so it's a sacrifice I'm willing to make. I hope that descriptive alt tags will help.

On the other hand, the whole text is there from the start and every other way is wrong.

WillPostForFood4• 3 years ago

it hurts SEO. In my case the user can live without those images, so it's a sacrifice I'm willing to make.

This is one of the big problems with the modern web, It puts you in this doom loop: sacrifice the user to please Google to get users.

donatj2• 3 years ago

I feel this. So much of what I do to appease Google Search Console ends up actually hurting the user experience. Blind ruled lacking of context.

nicbou2• 3 years ago

I agree wholeheartedly, although for the most part the performance metrics match my needs as a user.

In this case it means preserving bandwidth unless it's needed. I lazyload images for the same reason I serve 4 different image sizes.

dgb233• 3 years ago

The performance metrics in pagespeed/lighthouse etc. are not really assessing performance directly.

You can have a slow, bloated website but great metrics, because you’re doing the “right” things.

However lazy loading images that are not on screen is generally a good thing. Images are typically the heaviest part of a website and loading them only when needed is good.

The article in question acknowledges that, but is criticizing the implementation and failure mode.

darkclouds• 3 years ago

In the early days, google used those alt tags to help its SEO, but now we have the Eli Parsier Google filter bubble to give us the SEO experience we are looking for as it tries to combat those bots manipulating Search.

toast0• 3 years ago

Back in the olden days when I was closer to the web, and we didn't have the browser to do lazy loading for us, we would always load everything 'below the fold' after a timeout, if the user hadn't scrolled down (or left the page). Seems not unreasonable to not load images that aren't visible during the initial load, but pull them in a bit later. There's some priorty things you could try, but priorities don't always work the way we might want.

MDN says img lazy doesn't work unless javascript is enabled, so easy peasy to use javascript to make the images unlazy after onload.

brink• 3 years ago

Eh, mistakenly clicking an ad or irrelevant content when trying to click a link because the page loaded some async content at the last millisecond is far worse.

WillPostForFood4• 3 years ago

It is all bad because now all the images are async content too.

mouse_• 3 years ago

They do that on purpose.

lancefisher• 3 years ago

It’s a data driven decision. They a/b tested and found users were more interested in clicking on ads when images were lazy loaded.

highwind• 3 years ago

There used to be a time where you can load up a YouTube video on the site and go offline then watch the video.

You can't do that any more, unless you actively find a way to download the said video.

deadmutex• 3 years ago

You can do it with YouTube premium

earthboundkid2• 3 years ago

Or use whatever YouTube-dl is called now.

TylerE• 3 years ago

Uh, youtube absolutely has a save for offline viewing option.

lxgr8• 3 years ago

In the browser and without paying for Premium on mobile?

Lammy• 3 years ago

Lazy loading also allows any network operator (and FVEY et al) to surveil your progress reading any particular web page based on when the additional image requests are generated.

rcme3• 3 years ago

How are they inspecting your network traffic?

hunter2_7• 3 years ago

They aren't going to see behind the TLS curtain, but they would see (assuming no DNS encryption) a domain name lookup followed by various traffic patterns; either:

Bursts (page loads) with near silence in between, maybe just some non-human-triggered traffic from scripts that poll.

Bursts (page loads) with quite a bit more of a human-triggered cadence in between, if lazy loading during scrolling occurs.

But mouse-tracking analytics probably result in a similar leak, if not better.

matheusmoreira2• 3 years ago

They don't need to. They can infer based on the size and timing of the transfers. Nothing for a while then suddenly a huge download? Probably a picture. If the sizes are unique enough they might even figure out which.

https://en.wikipedia.org/wiki/Traffic_analysis

To stop this, we'd have to saturate the link 100% of the time even when no useful communications are taking place.

justin_oaks• 3 years ago

There's no way to disable Lazy Loading on Android Chrome or Android Firefox.

I would think you could effectively disable lazy loading by using a bookmarklet for individual pages, or a userscript in Tampermonkey for whole sites or patterns of sites.

It's not as simple of a solution as a browser option, but I figure solving your problem beats complaining about it.

dools• 3 years ago

If you open an article on a train you could always scroll to the bottom of the page before you start reading it in order to load all the resources.

hunter2_7• 3 years ago

There ought to be a "fringe reception mode" (extension, perhaps) which automates that, ideally without the user noticing. Just as TFA calls for.

lxgr8• 3 years ago

To me, that’s one of these “reading mode” apps.

It works ok most of the time, but I really wish there was a standard for that that browsers could just implement, rather than these (often centralized) apps having to reverse engineer it.

The one I use even belongs to a browser vendor, yet they’re trying to constantly upsell me a premium subscription.

vhcr2• 3 years ago

The decision here is completely on the hands of the user agent, use a browser that let's you disable lazy loading.

donatj2• 3 years ago

I hate it soooo much. I've got Gigabit Internet and it makes it feel like I'm back on dialup waiting for images to load as I scroll rather than having the page ready for me.

smasher164• 3 years ago

Even if network conditions are great, lazy loading breaks browser operations like "Find" with Ctrl-F. It's only gonna search what's in the viewport. I think lazy loading should only be used when there's an actually infinite stream of content to load. But stuff like the twitter replies section shouldn't be this way. I shouldn't have to scroll all the way down to make sure search works.

hunter2_7• 3 years ago

I'm not typically a Jira hater (I know, I know) but this is definitely a gripe I have with it. The backlog view lazy loads. Tiny little scraps of text! Ok so there's rank, priority, and maybe a few other data points to query for. But still, come on!

chrismorgan5• 3 years ago

This article is talking specifically about <img loading="lazy">, not progressively-loaded content, which is quite a different kettle of fish.

(Specifically, everyone agrees progressively loading your content is to be avoided if possible, whereas “add loading=lazy to your images” is common performance advice.)

ed_mercer2• 3 years ago

lazy loading breaks browser operations like "Find" with Ctrl-F. It's only gonna search what's in the viewport

Sort of. If you quickly add a letter and then remove it while the page is loading it'll refresh the results though (sort of like a React force re-render)

SoulMan• 3 years ago

I like such short article given the attention span I have these days. This could have been a tweet.

pradn4• 3 years ago

Hardly any app is designed for subway riders. If they were, we'd have widespread preloading (like half an hour of tweets pre-loaded), seamless delayed posting (sending a new post when the internet comes back online), and visibility into what's downloading and uploading so users can make informed choices. As with all accessibility affordances, this will help people beyond the targeted group - like air travelers, folks living in rural areas, or those out of the country without service. They say wifi coverage in trains is going take another 25 years in the NYC subway system. Until then, I hope we pay more attention to users with intermittent internet access.

lstamour2• 3 years ago

I dunno, a number of apps I use on the subway are designed for such uses, including audiobook apps, podcast apps and many news apps (e.g. The Economist). But yes, other apps that could be designed that way may not work as well as they should. But even Netflix and YouTube can suggest downloads in advance now. Some apps will never be fully updated - for example, while the standard Mail app works great offline (it's getting it to connect sometimes that seems to take forever), the Gmail app always wants to upload a photo fully to the cloud before sending an email and this trips me up every time, because it never shows a progress indicator and it doesn't allow the email to be sent in the background before attachments upload. It's amazing how in 2023, we have all these engineering resources and lessons that can be learned from apps like WhatsApp, but we still build apps that assume always-on connectivity. It makes sense - even my local subway system is getting cellular service these days - but it's still doubly irritating if in an area with poor signal. (The signals poor, plus the app doesn't work or requires a re-launch, or... etc. etc.)

knallfrosch• 3 years ago

Love The Economist. They silently download the newest edition in the background, even when the app isn't open. I think a year ago the download was only triggered once you opened the page and went to "Weekly." Possible, but easy to forget.

pradn4• 3 years ago

I'm with you - a lot of them are, but too many are not. I personally use the NYT and FT news apps in the subway quite a bit.

In terms of pain points, the biggest is Safari. It gets rid of website state pretty quickly. I have tons of disk storage on my phone, why not serialize to disk? It could even be a "frozen" mode that still lets you scroll saved articles. It wouldn't be so useful for web apps, of course.'

unsupp0rted• 3 years ago

It's the subway where you are that's not designed for apps.

On Korean subways I stream video at max res throughout the ride.

yellow_lead• 3 years ago

Same in taiwan. I think they must have cellphone antennas underground

belugacat• 3 years ago

The infrastructure of Asian capitals is the best in the world, that's exactly the point - 99% of the world experiences deteriorated network (see comments in this thread to that point). It's frustrating when software isn't built in ways that are resilient to that.

pradn4• 3 years ago

We're always going to have situations with intermittent network connections. It's best to design for that from the first. An offline-first experience is good even if you have a good network connection: lower latency (read from disk) and lower energy (the phone radio will be on for less time).

aaomidi3• 3 years ago

If you have Youtube's paid version, you can have the app automatically preload content it thinks you'd like.

This has saved my ass plenty of times when my ADHD brain needed content in places where I didn't have internet.

akdor1154• 3 years ago

That sounds like paying a subscription for a crack dealer in a rehab centre :p

ikmens• 3 years ago

you can also just download some videos from youtube you know you want to watch and save yourself the cash

ipaddr• 3 years ago

The game metro is unsurprisingly good. Turn based games work well.

underwater• 3 years ago

I'm not surprised that this is the case (I've made that same decision myself). But there are some apps that I just done understand: airline ticketing apps, theme park apps, etc. How is handling offline usage not ofne of the first requirements.

pradn4• 3 years ago

Gmail does not cache email attachments so ticket attachments are always iffy at busy venues. I usually just screenshot the ticket QR code now so I have it no matter the network situation at a crowded event.

chrismorgan5• 3 years ago

There's no way to disable Lazy Loading on Android Chrome or Android Firefox.

I haven’t tested it, but I would expect that Firefox for Android would still support going to about:config and changing… hmm, looks like dom.image-lazy-loading.enabled is no more, so I suppose you can just set dom.image-lazy-loading.root-margin.bottom to an enormous number (probably don’t need to worry about top/left/right, but you can do them for good measure if you want).

iggldiggl• 3 years ago

If you'd tested, you would have found that unfortunately access to about:config has been disabled on the release (and I think Beta, too?) versions of Firefox for Android.

chrismorgan5• 3 years ago

Back when I was using Android, I ran Firefox Nightly, just like I do on my laptop, so I knew about:config worked! I was not aware it was disabled on release, which seems pretty roundly just a silly and unreasonable restriction.

chupchap2• 3 years ago

Why did we go from pre-rendered pages generated with multi-threading on a server to single threaded javascript sequential loading in the front end?

afavour• 3 years ago

That has nothing to do with the complaint here.

chupchap2• 3 years ago

I thought this was the reason behind increasing use of lazy loading, especially in the context of non-live data like images and text

jiqiren• 3 years ago

This is a solved problem with Safari since at least High Sierra days. You add any webpage to your reading list and with appropriate settings you'll have a full local copy.

https://support.apple.com/guide/safari/keep-a-reading-list-s... relevant quote below...

Save a page in your Reading List to read when you’re not connected to the Internet: Control-click the page summary in the sidebar, then choose Save Offline. You can also swipe left over the page summary, then click Save Offline. To automatically save all pages in your Reading List, choose Safari > Preferences, click Advanced, then select “Save articles for offline reading automatically.”

mcny2• 3 years ago

I would like something similar for Mozilla Firefox.

On a very basic level, maybe Mozilla Firefox reader view can ignore the loading equals lazy hint and load all images. One step deeper, maybe we can keep these articles in some kind of local cache?

Come to think of it, what happened with Pocket, that Mozilla acquired? We were supposed to open source the pocket server like five years ago. Did it happen? Does anyone even care about pocket (the read offline app) anymore?

Edit: https://github.com/Pocket/extension-save-to-pocket/issues/75

acyou• 3 years ago

Subway riders are a corner case. The amount of energy, bandwidth, resources saved with lazy loading must be staggering.

Travellers may someday (and some do now) look back on losing signal with fondness. A time to reflect, meditate, plan, create, stop consuming for a little while, a welcome break.

edent2• 3 years ago

Several million people ride the London Underground every day. https://tfl.gov.uk/info-for/media/press-releases/2022/februa...

You're welcome to meditate if you want while crammed into a stranger's armpit. The rest of us would just like to read the news or catch up with our friends.

eviks2• 3 years ago

In what fantasy is loud subway a place to mediate and reflect?

tobyjsullivan• 3 years ago

Seems fixable at the standards level. The spec could define `loading="lazy"` as a (strong) hint for the client, but not a rule. Meanwhile, clients should allow disabling lazy loading. (The same way a valid client can disable Javascript, for instance.)

This is only a partial solution as no more than a tiny minority would think to actually disable lazy loading. But at least there would be an option for the author and others who operate in contexts where the lazy loading is harmful.

chrismorgan5• 3 years ago

It is a hint, inasmuch as the behaviour depends on the lazy load root margin which is implementation-defined, with a handful of suggested factors to take into account in choosing the defaults. Disabling lazy loading is done by setting the lazy load root margin infinitely large. Relevant spec: https://html.spec.whatwg.org/multipage/urls-and-fetching.htm.... In Firefox, you can control this by setting the dom.image-lazy-loading.root-margin.{top,left,right,bottom} prefs in about:config.

mikae12• 3 years ago

There's no way to disable Lazy Loading on […] Android Firefox.

  about:config

  dom.image-lazy-loading.enabled

aaomidi3• 3 years ago

Thank you!

edent2• 3 years ago

That doesn't work on the Android version of Firefox. It goes to a blank page with no settings.

See https://connect.mozilla.org/t5/ideas/firefox-for-android-abo...

chrismorgan5• 3 years ago

Huh. Excluded from stable? That’s a bit silly. I only used Nightly and it worked there last time I tried (maybe a year ago).

mikae12• 3 years ago

Sorry, I use (and recommend) the Iceraven fork for Android. Works there.

perilunar• 3 years ago

If the images are important to you, just scroll to the bottom of the article before reading to force the loading.

Also: it's a pity that the lowsrc attribute was deprecated. I know there are alternative using JS, but it was useful.

youngtaff2• 3 years ago

I’d like to see lowsrc return and renamed something like a placeholder attribute

kazinator• 3 years ago

Images are often junk though. What's better: to have the text of the article to read through the tunnel? Or some bullshit stock images that bear no relation to the story.

In the now olden days of the internet, people on low-bandwidth connections used proxies that stripped away images.

eviks2• 3 years ago

The issue is, as usual, the lack of convenient user control to match the behavior best suited to that user's specific situation

wruza3• 3 years ago

Not a subway rider, and I hate another form of lazy loading: webstore filters. You go to buypc.com, pc parts / ram, check 16GB box, it starts loading. Later you check 8GB (it starts loading), uncheck 16GB, it starts loading again, check “2x kits”. As you may have guessed already, it starts loading. You see the page and want to scroll it, but the second load finishes and the content changes. Then the third. If you want to filter a list by a handful of parameters, there will be almost the same amount of loads and re-renders, all insanely latent. A cherry on top - every time you check a box, load completion routine scrolls the page back to the top, so you miss a couple of clicks and check wrong checkboxes.

The irony is that a full category list in json format that could be instantly filtered at the client side would be smaller in size than a couple of jpegs they serve with each product card. And that would make their servers rpm literally an order of magnitude less.

djoletina• 3 years ago

If I understand correctly your beef is with the fact that they don’t have an “Apply filters” button and not lazy loading?

Also they’re probably not trying to save bandwidth but database servers.

RamRodification2• 3 years ago

Not OP, but I think the beef is that the act of applying a filter requires a reload of anything at all ("hey, server, please send me the list of only 16GB pairs this time"), when it's perfectly possible to just send the full list of items to the client initially and then have filtering apply instantly, client-side, on that already loaded list.

At least that's the beef I have, and was reminded of when reading the parent comment.

wruza3• 3 years ago

I just don’t get it. There’s nothing that could beat an one-time json download per product category. Not even “apply filters”, which I see less and less often with years. Unless a store has thousands of products and vague categories, ofc (but not in my cases).

If there is something beyond Hanlons Razor, I’d like to understand by which metric it works and how. E.g. how fetching 30 rows 10 times through different params compares to fetching 200-300 rows once, assuming various sorts of caching, etc. If everyone does it, it’s either a common methodic or a common ui-fad incompetence. But then even a shallow search should yield at least some results. It doesn’t.

wkat42422• 3 years ago

Yup or sometimes even you click another filter while it's loading and the other filter click just gets turned off again after the reload.

Very bad UX

rwoerz• 3 years ago

I particularly dislike lazy loading if it is rather a form of procrastination, i.e., web frameworks and runtimes that defer class loading, initialization and the like until the first request comes in (as if there is hope that this would never occur) but report to be "started/ready" before.

plaguepilled• 3 years ago

Its not a fix, but whenever I have to travel I set up a "reading list" on my RSS feed. Between that and physical books, I tend to fill in the time.

Actually, in general I would like to see RSS (or even a more draconic, constrained form of RSS) be a relevant web standard for traditional information dense webpages.

HocusLocus• 3 years ago

How's this for "lazy loading"? My Kaios fake-android Alcatel flip phone (sold to me by Verizon) shows the "time" the moment you remove it from the pocket and open it up.

Then you start counting to yourself: one one thousand, two one thousand, 3, 4, 5, 6...

After about six seconds, sometime a little less, the display updates to show the current ACTUAL time. The one it shows before that could be 5,20,40 minutes or up to an hour and a half, AGO.

I have never hated a phone so much. My hatred is palpable and intense. Of course the so-called-OS is the "latest" version which is only because Verizon abandoned it as soon as they rolled it out. And there are no options available that change this broken behavior.

throwg• 3 years ago

This is why my country has no subways instead we have flyways

jiofj• 3 years ago

In firefox you can set dom.image-lazy-loading.enabled to false

fishywang• 3 years ago

I wrote some code to convert links to epub, and those lazy loading images used in some websites used to be a huge pita to find the correct image file to be packed into the epub file, until I figured out a common enough way to handle them: https://b.yuxuan.org/lazy-loading-image-url2epub

theandrewbailey• 3 years ago

On my blog, I have a script that goes through lazy loaded images (which is all of them) and flips one to eager (in order down the page) every 5 seconds. Keep a page open for a minute, all images will be loaded, but if you close after 10 seconds, almost nothing extra is loaded.

I think I kind of hate lazy loading

Related Stories