Mateus

@normplum@fosstodon.org the main benefit would be not downloading the hundreds of images. If the user never advances past the first page, they never need to download more than the first page's images. Depending on the size of the images, that could save tons of bandwidth. A few lines of purpose-built JS could go a long way. But, pulling in a huge library for that purpose would negate the savings. So, choose carefully

@normplum@fosstodon.org I don't know the specifics off the top of my head, but most modern browsers will delay loading images until they're shown, so if you just keep them in a 'display: none' container, you should see that they don't actually get loaded until you page to them. If that doesn't work, you can just store the image URLs in a JavaScript array or some other tag, and then render them as actual image tags only when the user is on that page

@troy@opencoaster.net @normplum@fosstodon.org thank you. I knew it was something easy like that, but couldn't remember or be bothered to get to a computer to look it up 😂