Closed Bug 1405913 Opened 8 years ago Closed 8 years ago

selecting hide images does not automatically hide images anymore, required reload of the page

Categories

(Firefox for iOS :: General, defect, P2)

Other
iOS
defect

Tracking

()

RESOLVED INVALID
Tracking Status
fxios ? ---

People

(Reporter: njpark, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #1405331 +++ iOS: 11.0.1 Steps to reproduce: Case 1 - On iPhone (11.0) 1. Go to www.google.com 2. Open the menu and tap "Hide Images" Expected: Google logo is hiddle Actual: displayed page is unchanged Workaround: reload the page manually. Found it while running XCUITests/NoImagedTests.swift
Closing, discussed the feature behaviour changed to do this (No-Jun is updating the tests as a larger body of work for Photon)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID

Firefox ios v 18.1 (15719) Hide Images is broken since last update

Since the ios update on the 17th July 2019, the Hide Images option does not work. Firefox ios v 18.1 (15719)

Steps to reproduce:

1.  Start FF
2. Settings -> enable Hide Images
3. Open any website.
4. All images are loaded and displayed
5. Settings -> Toggle Hide Images : Result Images are hidden.
6. Open new tab with Hide Images enabled -> Images are loaded and displayed. 

In other words, I have to load a site with images first before I can hide the images, which defeats the purpose. Before the update I could open sites with Hide Images enabled and the images did not display ( and I hope were not downloaded).

My mobile data plan is back to being raped, and I've stopped surfing, because I only used Firefox because I have a 500Mb mobile data plan per month.

Is this a known problem or an intentional change/Feature?

Regards.

Hi, Soph. Thanks for your contribution. This is not a intentional change. This is a new issue that we will track and discuss here : https://github.com/mozilla-mobile/firefox-ios/issues/5270.

Hi Simon, Thank-you so much for the confirmation. An hour earlier I opened a bug here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1567162

Many thanks, Soph

You need to log in before you can comment on or make changes to this bug.