yep, new feature, probably a bug

unpoly still crushing

Alright. I think I have an interesting issue here. I'm loading a product cards (each containing an image) in a paginated list (with a "load-more" strategy using

hx-get

). On loading the page, let's say 6 images start to load. Then I hit "load more", 6 new images are added to the network queue. Before everything can finish loading, I hit one of the card, sending me to one of the product page using

hx-boost

. Everything works, but looking at the network tab, I can still see chrome trying to load the images from the last page, delaying (I think) the ones from the page I am currently on. I can really see this becoming a bottleneck when loading huge list of items on a poor network. Is there even a way to pause the browser from downloading assets?

Would something like

hx-sync

help you out? https://htmx.org/attributes/hx-sync/

Seems to be to sync (or queue) stuff INSIDE of HTMX. The problem I see in my use case is that the requests for the assets are already in progress and downloading. It's kind off in the hands of the browser at that point.

stackoverflow claims that clearing out src attribute should do https://stackoverflow.com/questions/5278304/how-to-cancel-an-image-from-loading

Not sure how to implement that ergonomically tho

Good start. But then HTMX will cache a page with no image.

I'll have to re-set the src on

htmx:load

hoping the browser cache to do it's thing

I'll take a look around other frameworks, try to see if it's an "internet problem" rather then a HTMX one. 😅

Svelte/Sveltekit seems to be doing the same...

Same for React

well damn. it's an internet thing.

We are as bad as everyone else 🎉

there's a 6 connection limit in http

hehehe well htmx seems to be handling the browser going offline better than Svelte with what Ive been looking at

(iirc it's actually 2 in the spec but browsers use 6)

serving http/2 might fix it

how does deniz know everything

Im already on http2 with Cloudflare. I'm just surprised there is no API to tell the browser to pause a request

I've seriously nerd-snipped myself with this one.

Time to re-read the whole MDN site... Actually, This might be a good use-case for a ServiceWorker. 🤓

> I can really see this becoming a bottleneck when loading huge list of items on a poor network. are you using

loading="lazy"

?

might prevent you from loading a huge number of images, hopefully making the bottleneck negligible

anyone try inertiajs?

Yes. But once the request is in flight, there is no canceling it. I'm kinda deep into optimization territory here. The impact is probably negligible for most users, but again I'm not doing it for "most users", I'm kinda aiming for "worst position to be as a user".

\> not optimizing for running the server locally on your machine because you are a developer 😏

Yeah . I try to optimize for "deep in the wood with a missing limb, bleeding to death with 1% battery and half a bar of 2g signal"

ah, I see, a fellow montanan