Remove loading='lazy' to fix firefox scroll-to-start bug #866
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using infinite scroll in firefox, you can sometimes automatically scroll back to the beginning when you reach the end of an archive for the first time . This happens because of a conflict between firefox's lazy loading behavior and progress tracking.
Firefox is pretty aggressive when it comes to lazy loading, and thus only loads images when they hit the viewport (or is at least very close). Also, LRR waits until the browser has loaded all images before jumping to the current page (according to progress tracking). Therefore, in firefox, the "jump to the correct page" only fires when you reach the end of the archive.
Chrome doesn't really suffer from this, as chrome's interpretation of lazy loading is basically "lol no" and tends to just load everything eagerly.