|
You are right to be annoyed, and the screenshot is what let me find it. I had been answering the wrong bug.
There were two of them. The one I fixed in 1.10 was vertical: the next page's first line bled in under the current one. Yours is horizontal, and it is a different cause. I set the gap between columns to 30px when I was trying to reclaim the landscape margins. Readium turns a page by scrolling exactly one screen width, but CSS advances the columns by column width plus that gap, so every page turn leaves the text 30px further along than the scroll went. It piles up until you are looking at two half pages, and it starts over at each chapter because every chapter is a separate document. That is exactly the pattern you described, and it has nothing to do with your device or your settings.
I measured it on an iPad Pro: with the gap in, the text block moved 60px right on every page turn (two columns, so twice the gap). With the gap set back to Readium's default of zero, it stays put — 79px, 77px, 81px across the same page turns, which is measurement noise.
The gap was there to keep the two columns apart on a wide screen. That job belongs to the page margins instead, so it goes.
The fix is in the build I am submitting now, not in the 1.11 you have. I am sorry it took two attempts and a screenshot from you to get to the real cause.
Jon — the font weight change did ship in 1.11, so you can test that one now. Changing the control while a book is open redraws the page you are on instead of waiting for the next open. What it still does not do is drive a variable font's weight axis; I am not claiming that part is done.
|