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
[Epub reader] Pagination not resetting scroll #1727
Comments
navigation.bug.mp4 |
Hi, I need some more context as the video, while helpful, isn't clear. Is the reader not scrolling back to top for you automatically? This is something that's working on my local, what version of Kavita are you running? |
Correct. When using the navigation arrows, it moves as expected. When using
tap pagination, it does not do that. My version is 0.6.1.0
…On Mon, Jan 9, 2023 at 18:29 Joe Milazzo ***@***.***> wrote:
Hi, I need some more context as the video, while helpful, isn't clear. Is
the reader not scrolling back to top for you automatically?
This is something that's working on my local, what version of Kavita are
you running?
—
Reply to this email directly, view it on GitHub
<#1727 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUMWUAF6NZD5AXHCNRGV4DWRSUPFANCNFSM6AAAAAATTJBIYE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This is already fixed in the nightly and will be in the upcoming v0.7 release. I have however added it to the release shakeout testing matrix so it doesn't get missed again. Appreciate the bug report. |
Describe the bug
When navigating using tap pagination on a mobile device, moving to the next page does not take the reader to the top of the next page.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected behavior would be that when the reader taps to advance, they are taken to the top of the next page.
Screenshots
SEE below FOR VIDEO.
Desktop (please complete the following information):
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: