Some desktop builds expose a web-reading action for HTML articles. Publisher pages can depend on scripts, authentication, network access or site policy, so a page that opens in another browser may behave differently inside the app.
When to try it
Try the web view when a saved or search result has an article page but no usable PDF, and the current build exposes an HTML or web-reading action. Publisher pages can depend on scripts, authentication, network access or site policy. A browser page that opens in another browser may still behave differently inside the app.
Basic workflow
- Open the selected article or saved record.
- Use the HTML or web-reading action that is visible in your build.
- Check that the page title and article content match the selected paper.
- If the page remains blank or shows the wrong article, record the build, article source, visible title and the action sequence.
- Keep the original article link and use a publisher PDF or a local copy when available.
Offline access, publisher login, interactive figures, supplementary files and page persistence depend on the site and the current build. Keep the saved record and original article link if embedded reading does not work.
Troubleshooting
If the reader is empty, first check the same article URL in a regular browser and confirm that the desktop build has network access. If the regular browser also cannot load it, the cause may be site access or the network. If only the embedded reader fails, note the site and error for support.
Do not clear the Library or cached data as a first step. A page load failure does not prove the saved metadata or original PDF is damaged.
For PDF reading, see PDF Viewer. For saved and imported items, see Library & Local PDFs.