Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Bookmarking pages in Reader-Mode won't save them for offline-reading

  • 3 replies
  • 22 have this problem
  • 1 view
  • Last reply by faehkerlohl

more options

As of today, bookmarking pages in Reader-Mode won't get them saved on my phone. It worked without a hitch until the newest update (as of writing this article, Firefox 53 for Android).

Usual procedure: 1) Visit any site on Firefox and activate the reader-mode through tapping the book-icon in the right-hand side of the url-bar. 2) Reader-Mode activates; the book-icon turns orange to indicate thusly 3) Opening the menu and tapping the star-icon to bookmark the site

Expected behavior: Book-Icon turning blue, indicating the site got saved locally and is accessable through the reading list

Occured behavior: Book-Icon stays orange. A message at the bottom pops up and informs me that the site got bookmarked. When trying to open the site in the bookmarks, it reverts back into the non-reader mode and completely reloads the site through the active connection. Deactivating Wi-Fi (or data) nets an error due to having no internet connection.

This occurs for every site that lets me turn the reader mode on - whether it being a site that worked before or a completely new one I tried the first time.

So, to sum it up, I can't save pages to read offline - which is, like, 80% of the reason why I use Firefox for Android in the first place, as I could do it without installing any other extensions etc.

Hardware: OnePlus 2 (ONE A2003) Android Ver: 6.0.1 ROM-Version: 3.5.8 (OxygenMod) Free storage space: 70%

As of today, bookmarking pages in Reader-Mode won't get them saved on my phone. It worked without a hitch until the newest update (as of writing this article, Firefox 53 for Android). Usual procedure: 1) Visit any site on Firefox and activate the reader-mode through tapping the book-icon in the right-hand side of the url-bar. 2) Reader-Mode activates; the book-icon turns orange to indicate thusly 3) Opening the menu and tapping the star-icon to bookmark the site Expected behavior: Book-Icon turning blue, indicating the site got saved locally and is accessable through the reading list Occured behavior: Book-Icon stays orange. A message at the bottom pops up and informs me that the site got bookmarked. When trying to open the site in the bookmarks, it reverts back into the non-reader mode and completely reloads the site through the active connection. Deactivating Wi-Fi (or data) nets an error due to having no internet connection. This occurs for every site that lets me turn the reader mode on - whether it being a site that worked before or a completely new one I tried the first time. So, to sum it up, I can't save pages to read offline - which is, like, 80% of the reason why I use Firefox for Android in the first place, as I could do it without installing any other extensions etc. Hardware: OnePlus 2 (ONE A2003) Android Ver: 6.0.1 ROM-Version: 3.5.8 (OxygenMod) Free storage space: 70%

Chosen solution

This is a known issue with this release. I am not sure when it will be fixed.

Read this answer in context 👍 2

All Replies (3)

more options

So, do I have to wait until the next Firefox update or should I search for alternatives?

more options

Chosen Solution

This is a known issue with this release. I am not sure when it will be fixed.

more options

kbrosnan said

This is a known issue with this release. I am not sure when it will be fixed.

Thank you for the clarification! Is there a bug tracker entry for this particular bug that I could follow?