top level domain blocking enabled with Standard
blocking - follow up to #15095
#15242
Labels
bug
feature/shields
The overall Shields feature in Brave.
OS/Android
Fixes related to Android browser functionality
OS/Desktop
privacy/feature
User-facing privacy- & security-focused feature work.
privacy-pod
Feature work for the Privacy & Web Compatibility pod
QA Pass - Android ARM
QA Pass - Android Tab
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-All-Platforms
QA/Yes
release-notes/exclude
Milestone
Description
As per #15095, we should be disabling top level domain blocking in
Standard
mode and should only be blocking when a user has selectedAggressive
via the Brave Shields settings.Steps to Reproduce
1.25.10 Chromium: 90.0.4430.61
used in this case)1-1ads.com
,actionsplash.com
orpub.chez.com
interstitial
page is being displayed which means top level domain blocking is occurringActual result:
Top level domain blocking is occurring even when
Standard
is selected as the default shields setting.Expected result:
Top level domain blocking should be disabled on
Standard
and only enabled when a user has selectedAggressive
mode.Reproduces how often:
100% reproducible using the above STR.
Brave version (brave://version info)
Version/Channel Information:
N/A
(being disabled via Disable domain blocking via feature flag brave-core#8507Yes
Yes
Other Additional Information:
N/A
N/A
N/A
Miscellaneous Information:
CCing @rebron @bsclifton @brave/legacy_qa @pes10k @pilgrim-brave
The text was updated successfully, but these errors were encountered: