Open Dero99 opened 3 months ago
I'm going to need some more info about your reader settings to get an understanding for reproducing.
I use the reader 2-3x a day. This issue seems to be maybe weekly, today was first time since weekend. I always read until chapter break as those pages are easy to find if the fault happens.DarrellOn Jun 27, 2024, at 10:57 AM, Joe Milazzo @.***> wrote: I'm going to need some more info about your reader settings to get an understanding for reproducing.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
I need reader settings to be able to try and reproduce the issue. I can't really help until you provide more information.
So when you re-open the page, it's on the same device but instead of a virtual page of 1, you're on page 3 or likely actual page of 39 and the last virtual page of that actual page?
Note: When in column mode, the real pages (which can be whole chapters usually) are split up into virtual pages. That is what that top progress bar indicates. Progress is stored per real page and at runtime, Kavita recalculates the virtual page and identifies the last html element that was in view and scrolls to it to resume position (some skew is expected).
What I see is I close reader at chapter 12, page 1. When I reopen reader I’m three pages ahead, chapter 12, page 3. I always use the same device, same orientation.
On Jun 28, 2024, at 7:10 AM, Joe Milazzo @.***> wrote:
So when you re-open the page, it's on the same device but instead of a virtual page of 1, you're on page 3 or likely actual page of 39 and the last virtual page of that actual page?
Note: When in column mode, the real pages (which can be whole chapters usually) are split up into virtual pages. That is what that top progress bar indicates. Progress is stored per real page and at runtime, Kavita recalculates the virtual page and identifies the last html element that was in view and scrolls to it to resume position (some skew is expected).
— Reply to this email directly, view it on GitHub https://github.com/Kareadita/Kavita/issues/3022#issuecomment-2197024753, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDHY7SPI3PGZIMLMNLYFHLZJVVF3AVCNFSM6AAAAABKAJA5K2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGAZDINZVGM. You are receiving this because you authored the thread.
Tried ending session differently, instead of X and Home, iOS app switcher, I just app switched when I was done reading. For the next 5 reading sessions, pwa launch Kavita, goes to Home and I select the epub, continue where I stopped correctly. Last try this method failed, 4 pages ahead of stop point.
Thanks. I'll take a look and try to reproduce.
Similar problem here, it seems to only mess up if there's an image in the chapter. Using nightly 0.8.2.1, added reader settings and a video demonstrating.
Except for front and rear cover, no images in my epub. While originally the reader skipped 3 pages ahead, it now skips 10-14 pages when book opened.
What happened?
Reading a epub, eyes tired so click X on top and quit pwa app on iPad. Later sometimes when continuing that epub the current resume page is wrong. Might be three or more pages forward or previous.
What did you expect?
When finishing reading for day and then later continuing, expect the current page to be the page you quit at.
Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists.
0.8.1 - Stable
What operating system is Kavita being hosted from?
Mac
If the issue is being seen on Desktop, what OS are you running where you see the issue?
None
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Safari
If the issue is being seen on Mobile, what OS are you running where you see the issue?
iOS
If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?
Safari
Relevant log output
No response
Additional Notes
Created pwa on iOS, also using safari and chrome on iOS show this issue. also if orientation changes, current page really messes up.