Page navigation stops working when NeoReader V2 rendering engine is enabled
This report is about NeoReader version 23509-b25416c (23509), running on Onyx Boox Nova 3 with firmware 2021-03-31_20-31_3.1_0631e26.
I have noticed that a few EPUBs (specifically those produced by Apress), get stuck on NeoReader when the V2 rendering engine is enabled. In these instances, it is not possible to move to the next page, but it is (sometimes) possible to go backwards. Instead of moving forward, the screen refreshes but remains on the same page (i.e., the app itself is not frozen or crashed.) Sometimes, if the font size is increased or decreased, then forward navigation works, but other times all navigation (in both directions) stops working, or completely empty pages are displayed (in extreme cases, I have seen NeoReader report that the file has no pages!)
On the other hand, page navigation works fine with V2 engine disabled, but it is not ideal as all original formatting (as set by the publisher) is lost. As I said earlier, V2 works for 99% of EPUBs I have tried, with few exceptions.
My suspicion is that this happens in the boundary between text and images, for example when the current page ends with text and the next one starts with an image. Perhaps some attribute of the image makes it too big to be displayed on the next page, and then NeoReader refuses to navigate to that page.
The content of these EPUBs is copyrighted, so I cannot share it freely, but please let me know if there is something specific I can pass along in terms of the source code of the EPUB file for debugging.
-
Dear customer,
We apologize for the inconvenience. In this case, please try to reproduce the issue on your device, and then please immediately submit bugs/software questions on Feedback via Settings/ Feedback on your device. Please make sure that you tick the option "send logs" while sending the Feedback so that we can analyze and diagnose the exact problem better. Our technical team will reply to you in 2 working days after you submit the Feedback. Many thanks for your understanding.0
Please sign in to leave a comment.
Comments
1 comment