(Behavior confirmed on Brave browser and Chrome) When using "long-strip pre-rendering" the images are loaded progressively as the user triggers the "next page" action (either by clicking the right-side of the image or by clicking the right-arrow ) or by scrolling down using the scroll bar, mouse wheel, arrow keys, etc. When the image pre-loading can't keep up with the user's reading speed for whatever reason and the user trigger a next-page action when at the end of the page but is not at the end of the chapter, the web app appears to trigger a reload of the chapter, taking the user back to the beginning of the chapter, displaying a "loading" spinner and reloading the chapter from scratch. This is irritating for the user and it doesn't match the behavior when scrolling downward - if you scroll down to the end and attempt to scroll further there is just no activity.
I don't know if this behavior is a bug or if someone implemented it to ensure that chapter loading didn't time out, but from a user experience perspective it's pretty aggravating to thoughtlessly click to go to the next page and be taken back to the start and shown a spinner. I believe the better behavior would be to either do nothing or possibly to show a loading spinner while kicking off loading of the next image (which seems to be the behavior on Firefox). If loading genuinely has stalled, the user can reload the page on their own.
I don't know if this behavior is a bug or if someone implemented it to ensure that chapter loading didn't time out, but from a user experience perspective it's pretty aggravating to thoughtlessly click to go to the next page and be taken back to the start and shown a spinner. I believe the better behavior would be to either do nothing or possibly to show a loading spinner while kicking off loading of the next image (which seems to be the behavior on Firefox). If loading genuinely has stalled, the user can reload the page on their own.
