-
Notifications
You must be signed in to change notification settings - Fork 774
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
Google Chrome - PDF File - Scrolling page counter bug #1333
Comments
@aophil Can you please share the link with me if it's on papermark.io |
Does that also happen on horizontal view? |
"@mfts I understand what he's trying to say. Please check out this link. If you use the scrollbar to scroll, the page number won’t update and will show the old page number and then, if you start using the icon button, it will first scroll based on the page counter |
It's possible that it takes longer to load because of slow network connection. typically we preload the first 5-10 images and then on next-page click we load the n+1 image. so if you rapidly click next, it may get stuck. I will look into it. i couldn't reproduce it with normal network connections tho |
Hi @mfts , Some people skim through the pages, so this frozen page # that won't follow the scrolling bar position in real-time can be problematic regarding user experience since pages just won't load as long as the page number is frozen. |
/award 150 |
Awarding aophil: 150 points 🕹️ Well done! Check out your new contribution on oss.gg/aophil |
Hi,
I am testing whether Papermark is a good alternative for the company I work for, so while testing it with our documents, I spotted a bug in Google Chrome.
When you open a PDF document with multiple pages (38 pages in my case) in Papermark and start to quickly scroll through them instead of pressing the ⬇️ arrow, the page counter freezes at page "n," and pages "n+4, n+5, n+6, etc..." won't load.
I have to go back up so the page counter refreshes/unfreezes and the pages start loading again.
(Ps: On Firefox no issue at all.)
The text was updated successfully, but these errors were encountered: