Reader mode often doesn't work on first try

[BrilliantThings]

Please write necessary information as described below. If information is not enough, I may not have time to look into it.

What device and app version are you using

• Device: Boox Page 7
• OS: 2024-07-01_14-54_3.5.3_7961252698
• EinkBro Version 11.13.0

Describe the bug
When I used reader mode it often only displays "undefined". Refreshing the page fixes it

To Reproduce
Steps to reproduce the behavior.

Example description:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
Reader mode should display full article text
Screenshots
I have attached screen recording

screen-20240824-064220.mp4

Additional context
Add any other context about the problem here.

[plateaukao]

Does it happen on all websites? or only some specific site?
If it's the latter, please provide the websites you encounter this issue.
ps. I tried www.thesaturdaypaper.com on my BOOX device, and it seems all work well to enter reader mode.

[BrilliantThings]

It can happen with any website, but not every time. It happens with The Atlantic, New Yorker, New York Times etc. Sorry, I’m not sure what steps make it happen.

[plateaukao]

Next time when it happens, please help to provide what behaviors you have done before it happens. (maybe clicking on any features in menu, or change any settings.)
I can't fix it if I don't know how to reproduce the issue.

[BrilliantThings]

Here’s another example. I did nothing before this happened.

screen-20240824-180231.mp4

[plateaukao]

I still can't reproduce it on my BOOX device. The Atlantic website works on my device too.
Did it happen before this version on your device? Is the same issue happen on your other devices with the same version?
Did you use any BOOX Page 7's system optimization for EinkBro?
If there's any information that might be helpful, please provide it.

[BrilliantThings]

System optimisation details

screen-20240825-131941.mov

attached

[BrilliantThings]

The first version I used was 11.11.0 and it was an issue with that version, too