As currently designed, the app uses lazy loading of thumbnails, e.g., as the user scrolls the list the thumbnails that haven't been downloaded but are coming into view are downloaded "just in time". This also applies to images in articles. That means that if the user hasn't opened a bookmark (but its content is downloaded) or if they have not yet viewed a portion of the list views (for example, has not scrolled to bottom or hasn't viewed Archive list yet) and they do so with the device offline, there won't be images/thumbnails to display.
A change such that all thumbnails are downloaded during bookmark sync or images during content sync would be an architectural change for the app. The UX implications of lazy loading are just in completeness of what is displayed, doesn't represent a functional deficiency, so I'm logging this as an enhancement issue for future consideration.
As currently designed, the app uses lazy loading of thumbnails, e.g., as the user scrolls the list the thumbnails that haven't been downloaded but are coming into view are downloaded "just in time". This also applies to images in articles. That means that if the user hasn't opened a bookmark (but its content is downloaded) or if they have not yet viewed a portion of the list views (for example, has not scrolled to bottom or hasn't viewed Archive list yet) and they do so with the device offline, there won't be images/thumbnails to display.
A change such that all thumbnails are downloaded during bookmark sync or images during content sync would be an architectural change for the app. The UX implications of lazy loading are just in completeness of what is displayed, doesn't represent a functional deficiency, so I'm logging this as an enhancement issue for future consideration.