cosmetic filtering doesn't handle vetted search engines correctly if they have subdomains #14248
Labels
features/shields/cosmetic-filtering
OS/Android
Fixes related to Android browser functionality
OS/Desktop
QA Pass - Android ARM
QA Pass - Android Tab
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
regression
release/blocking
release-notes/exclude
Milestone
Currently we do not apply cosmetic filtering to privacy respecting ads on search partners in the default setting (we still hide then in the aggressive mode). However, the check for "is this a vetted search engine" page fails incorrectly for search engine subdomain pages.
For example, currently cosmetic filtering is default off for https://startpage.com/sp/search (this is expected). However, its default on for startpage subdomains (e.g., https://www.startpage.com/sp/search). The same is true for all the expected, vetted domains.
The text was updated successfully, but these errors were encountered: