mirror of
https://github.com/bookorbit/bookorbit.git
synced 2026-11-03 00:11:37 -06:00
neon
68fae9a121
KOReader reports a paged document's position as a page number and a reflowable one's as an xpointer, but applySharedProgress treated every incoming position as an xpointer and upsertReadingProgress hardcoded pageNumber to null on every write. A PDF synced from a device therefore stored a correct percentage with no page, and the web reader reopened it at page 1. The same write also destroyed a page the web reader had saved earlier, including during an unattended bulk sweep, so this lost positions that were never synced from a device at all. Carry the book file's format through hash resolution and pick the column from it. CBZ/CBR were affected identically at the data level but masked in the UI, because the comic reader estimates a page from the percentage when none is stored. Closes #954