-
Notifications
You must be signed in to change notification settings - Fork 722
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
1 addition
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The previous filter still hides whole page for JP locale:
I think with this matces-css version
$shide
is no more needed, but double-check is welcome.5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why remove the
matches-path
filter ?5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ads are back at
https://www.google.com/search?q=DOOM+Eternal
www.google.*##[href^="/aclk"][href$="adurl="]:not(:scope > :upward([class^="sh-sr__shop-result-group"])):upward(3)
is needed.5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Yuki2718
It wouldn't in the presence of@@||www.google.*/search?q=*tbm=shop$shide
$shide
needs to made less specific then.5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean?
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't reproduce, what modification is needed?
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming shide is no more needed, but I may be wrong.
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added -
@@||www.google.*/search*tbm=shop$shide
Add the original filter and add that filter, shouldn't cause the breakage you mentioned in 5450034#commitcomment-56321446
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually causing with default setup, the path is slightly different.Okay you noticed that. And shide makes hiding ads impossible.5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$shide
is temp until:matches-path
filter is activatedIf nothing else I can make it specific to
.com
for now.5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested on the path transcribed from https://user-images.githubusercontent.com/58900598/132979597-3176c0ca-6138-48f6-9bf1-3b50f45bc1a4.png
and I don't see any breakage with the two filters I suggested to add.
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I mean no
q=
and you noticed that.5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't reproduce your issue on
https://www.google.co.jp/search?tbm=shop&hl=ja&psb=1&q=cars
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No wonder, just like I can't reproduce the missed ads.
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Yuki2718 Get a US VPN or a UK VPN and then browse to that url.
You misunderstand, I can reproduce your issue but not after modifying the
$shide
filter to cover .jp case which I did in 001aa6c5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can
##[href^="/aclk"][href$="adurl="]:not(:scope > :upward([class^="sh-sr__shop-result-group"])):upward(3)
be re-written like##*:not([class^="sh-sr__shop-result-group"]) [href^="/aclk"][href$="adurl="]:upward(3)
?5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I understand:
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the only issue is that missed ads, how about adding another filter for that? On my end my fix and removing shide correctly hides Sponsored products on shopping and search pages without FP. Tested both on US and JP locale.
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works fine, we can change to that. Does changing to that filter help with the JP locale case ?
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay now reproduced ads with US IP.
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those are not missed ads btw, Google started inserting products ads as of last month.
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But we will block them anyway, right?
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
##*:not([class^="sh-sr__shop-result-group"]) [href^="/aclk"][href$="adurl="]:upward(3)
works fine for them if you want to remove original filter5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
e6032f5
Now with this change, whether we still need
$shide
or not, I leave that upto to you.5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I want to remove $shide without waiting for the arreival of matches-path, if possible. They may change but until then matches-path will become available.
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only worry is that by removing
$shide
we may start seeing shopping pages breakage again and dealing with them again and again is tedious, so my preferance was to wait for the arrival of the stable build for us to use:matches-path
.5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, given the history. I'll leave them for now. The matches-css filter will become usuful once shide is removed so I'll temp comment it out.
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Yuki2718 Also would you mind modifying the regex in
www.google.*##:not(:matches-path(/^/search\?q=.*?tbm=shop|^/shopping/)) [href^="/aclk"][href$="adurl="]:not(> *:upward([class^="sh-sr__shop-result-group"])):upward(3)
to cover the current breakage JP locale issue as well ?5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@uBlock-user 2e40e0a
5450034
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revisited, I think we can remove $shide by replacing current filters with
www.google.*##*:not([class^="sh-sr__shop-result-group"]) #kp-wp-tab-overview g-dropdown-menu:upward(#kp-wp-tab-overview > div):has(a[href*="/aclk?"][href$="adurl="])
. Let's see if this still breaks pages.