![Firefox untuk iOS logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-37-48-1aeaf0_1.png)
Reader view on Firefox for iOS does not function correctly for a web site that I frequently visit.
The home page of that troublesome site is at www.brisbanetimes.com.au (home page). Firefox for iOS appears to work correctly on other sites. If I start on the home page and select a link to a news article then that news article's web page is correctly displayed. When I then select reader view I get a garbled version of the previous (home) page. I can clear the problem by toggling back and forth between the desktop version of the article and the mobile version, using the relevant item on "Page Actions". The problem is not evident on Safari. Firefox is my default browser. I am on iOS version 14.4 and have the latest versions of Firefox for iOS and Safari. Any (polite and helpful) suggestions please?
Semua Balasan (9)
Please close this bug report. When I upgraded to iOS 14.4.1 the problem went away.
Wrong! The problem didn't go away when I upgraded to iOS 14.4.1.
Hey Peter,
I can reproduce it in Firefox for iOS 32. But then upgrading to 32.1 fixed the problem. Can you try upgrading as well?
Sadly no. Upgrading to 32.1 didn’t solve the problem.
That's a bummer. Can you try to clear the website data to see if it fixed the problem?
You can try it from Settings -> Data Management -> Website Data. Then choose the one from the website above. Please be careful as you might don't want to remove the other website data.
Thanks for your continuing help Kiki, but what you suggested didn't fix the problem. And because I had auto-update switched on I am now on version 32.0 of Firefox and the problem persists.
Sorry to hear that, Peter. I'm run out of ideas, to be honest. But if you're on auto-update, you should be at 32.1 now.
I have a work-around that will do for now. If I refresh the page immediately before I invoke reader view on this web site then reader view works reliably.
Good to hear that. It seems that it's a cache's problem more than anything..