This only happens if the user has not re-loaded the article they were viewing. And on gong to the next page / article, or restarting the app, the issue goes away. It could perhaps be solved by forcing the app to re-load the current page when switching between modes.
This only happens if the user has not re-loaded the article they were viewing. And on gong to the next page / article, or restarting the app, the issue goes away. It could perhaps be solved by forcing the app to re-load the current page when switching between modes.