1144510 - Reader view content is cached permenantly

Status: RESOLVED FIXED

(Firefox for iOS :: Reader View, defect)

Description

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

To reproduce:

1) Go to news.ycombinator.com
2) Open some article
3) Enable reader mode
4) Hit back
5) Hit forward

Expected: you are back at the original page

Actual: you are back at the readerized page

The webview is caching the changed page content. There is no way to invalidate the cache.

This can be solved by serving the reader mode content from the local web server. Enabling reader mode would simply redirect to http://localhost:1234/reader-mode/$SOMEIDENTIFIER and render the readerized page.

This does result in an extra history entry but that would be parity with Firefox for Android where the same thing happens.

This does mean that we need to let the URL Bar understand that there is a difference between the displayed url (http://www.example.com) and the internal reader-mode url that is actually loaded in the webview (http://localhost/reader-mode?url=http://www.example.com).

And same for things like history, bookmarks, and sharing. because we do not want the internal URL to be used outside of our application. (it would be useless because the port is randomized)

Comment 1

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

This also solved the weirdness of using swipe gestures around readerized content.

Comment 2

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

Fixed as part of bug 1144511