Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Front page gallery images need 'loading' skeleton #185

Open
Lordfirespeed opened this issue Oct 24, 2024 · 4 comments
Open

Front page gallery images need 'loading' skeleton #185

Lordfirespeed opened this issue Oct 24, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@Lordfirespeed
Copy link
Member

due to image lazy-loading, slides are transparent on initial page load
image
we should either

  • give images a background which will be rendered while they load
  • render a 'skeleton' while the image is loading
@Lordfirespeed Lordfirespeed added the bug Something isn't working label Oct 24, 2024
@SkyePal42
Copy link

Use progressive image technique?
https://www.yzlow.com/progressive-image-loading-with-nextjs

@Lordfirespeed
Copy link
Member Author

the images don't take long to load, next already optimises them fairly well

Images for slides that are out of view by default don't get fetched until the slide is revealed; involving an image of any resolution in the placeholder will not resolve the issue, as those images will still have to be fetched (although fetching them would be quicker than fetching the fullres image) resulting in a lag before anything is displayed

we need a placeholder that relies only on html/css

@SkyePal42
Copy link

what about a durhack logo svg set as the image's background-image so that it is sent/embedded in the html/css and shows first before having the actual image load over it... i think that's how it works... yes it is :)
https://codepen.io/boomkiller1119/pen/yLmjrdx w/ throttle 3G and no cache -> can see svg load and then image loads on top
original codepen: https://codepen.io/jdsteinbach/pen/aQOZBE

@Lordfirespeed
Copy link
Member Author

yeah that would work but I feel that's gonna look tacky + overcomplicate something simple

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants