Opened on 09/24/2018 at 04:13:44 PM
Closed on 10/09/2019 at 08:26:27 PM
Last modified on 10/09/2019 at 08:26:56 PM
#6979 closed change (rejected)
Don't force the use of the Safari's native Content Blocking with Safari 12
| Reported by: | Just4Dev | Assignee: | |
|---|---|---|---|
| Priority: | Unknown | Milestone: | |
| Module: | Platform | Keywords: | closed-in-favor-of-gitlab |
| Cc: | Blocked By: | ||
| Blocking: | Platform: | Safari | |
| Ready: | no | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description
Background
With Safari 12, Adblock Plus force the use of the Safari's native Content Blocking. Users can't disable this to use the fallback content blocker which perfectly works with Safari 12 (I downloaded an older version of ABP where I did disabled the Safari's native Content Blocking and ads are blocked).
How to reproduce
- Click ABP icon
- Go to General
- Try to disable "Use Safari's native Content Blocking (experimental)" (checkbox disabled)
What to change
The new ABP app from the Mac App Store is missing a lot of important features (custom lists, ...) the use of the old extension (from the Safari Extension Gallery) is still the best way to use ABP, but the Safari's native Content Blocking is limited by the number of rules.
Because of that some ads are not blocked (like for example ads before a YouTube videos).
What I want is to be able to disable to use of the Safari's native Content Blocking.
Environment
Adblock Plus version: 1.12.5
Safari version: 12.0
macOS version: 10.12.6 (macOS Sierra)
Attachments (1)
Change History (4)
Changed on 09/24/2018 at 04:13:57 PM by Just4Dev
comment:1 Changed on 10/09/2019 at 06:33:57 PM by greiner
- Component changed from Unknown to Platform
comment:2 Changed on 10/09/2019 at 08:26:27 PM by sebastian
- Resolution set to rejected
- Status changed from new to closed
comment:3 Changed on 10/09/2019 at 08:26:56 PM by sebastian
- Keywords closed-in-favor-of-gitlab added
Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the new issue tracker.