-
Notifications
You must be signed in to change notification settings - Fork 971
whitelist script signatures #1353
Comments
this is a bug - TP/AB should not be blocking first party resources in the first place |
need @bbondy input. i would have expected |
I thought we already had this check but apparently not. We should just do an extra check to make sure the |
re-opening, I think a rule like this will fix: |
Audtiors: @lukemulks Partially addresses: brave/browser-laptop#1353
Audtiors: @lukemulks Partially addresses: brave/browser-laptop#1353
mostly fixed by the filtering rule committed above, but some things are still getting blocked that shouldn't (logo). I think it's a bug in the ad block library and could be a more generalized problem so blocking on this since the first party filtering change first lands in 0.20.x too. |
Never mind, I just tested with combined data file and it's working. I was testing before with custom adblock rule exception which runs in an independent instance |
heads-up I added a basic test plan please add more checks in case mine is incomplete. Thanks |
Test Plan
I recently went to adops.com and the site was basically unusable because they are on the blocking list. I don't really see any reason why we should be blocking jquery and other scripts that are not ad related. Not sure if a whitelist is the answer, but maybe consider the referrer url (when not in an iframe) because these are 1st-party scripts in this context.
The text was updated successfully, but these errors were encountered: