Closed Bug 1562041 Opened 7 years ago Closed 7 years ago

Firefox for iOS should ship with a content blocker

Categories

(Firefox for iOS :: Browser, defect)

Other
iOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: pshirshov, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.102 Safari/537.36 Vivaldi/2.6.1566.44

Steps to reproduce:

At the moment iOS Firefox has no content blocking capabilities similar to Android version where you may install uBlock Origin and other content blockers.

At the moment we have at least 3 iOS browsers supporting full scale content blockers:

  1. Safari
  2. Brave
  3. Microsoft Edge

It's a real disadvantage for Firefox not to provide users proper content blocking.

Thank you for reporting. Unfortunately this request has already been discussed at : https://github.com/mozilla-mobile/firefox-ios/issues/5198

Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID

It wasn't "discussed", it was closed without any sane explanation.

Tracking protection does not provide the same quality of filtering and control as full-scale content blockers do.

By full scale content blocking in Brave, Safari and Edge, do you mean the option to block all cookies with the risk of preventing some websites from working correctly?

If so you can go to Firefox Settings -> Tracking Protection and set it to Strict. Hope this helps.

In case of Safari I may install custom region-specific rulesets (for example, AdGuard provides a very broad choice) and define custom rules.

In case of Brave I have no controls but I didn't find any single webpage showing annoying ads under Brave. Same applies for Edge.

In case of iOS Firefox there are a lot of places where ads aren't blocked even with highest tracking protection level. In case of Firefox Android I may install uBlock Origin or whatever else and use all the filter lists I need.

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