-
Notifications
You must be signed in to change notification settings - Fork 697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
google.com: breakage, nuisance #23701
Comments
Worse if we can't remove filter (lack of alternative in stable selector for You should definitely make sure that the new cookie value does not globally unlock violence and nudity. |
|
Hmm. I can only reproduce occasionally. What exact steps are needed to reproduce this each time? Can you test with this filter?
It enables search customization but not personalized ads. |
I think we should not use |
@peace2000 That filter works for me, didn't produce this breakage. The direct link I provided earlier expired, so here's some more detailed steps to reproduce:
|
Yeah, the new rule doesn't have the problem. |
I'm still failing to repro. But as it's reproduced by others and I also managed to reproduce it few times yesterday, I believe it's probably best to change the filter. Though I'm bit puzzled as even if we allow search customization I'm still in doubt whether it affects Safe search functionality. Because Google describes search customization like this: " Also, when I change the Safe search setting, cookie called I'm wondering whether the issue is that the problematic filter was created last year and Google has someway changed the logic in their scripts how the cookie value is being formed and what values work properly. We need to figure this out, otherwise the new filter will break functions at some point also. @Yuki2718 @jackrjli if you are still willing, can you try this newly created "Reject all" filter?
Also as suggested by @stephenhawk8054 it might a good idea to remove the 1 year expire date and make the cookie last only for a session. |
@peace2000 Unfortunately that new filter breaks things for me again. |
Can confirm,
Shouldn't we use default expiration period? |
Default is session. |
For the scriptlet, session is the default expire time. Though Google sets the cookie expire time to 1 year and 1 month if generated naturally. I wonder if there's a use case when it matters what is set for the cookie expire date. Anyway, updated the filter 8196b3e |
Prerequisites
URL(s) where the issue occurs.
https://lens.google.com/search?p=AbrfA8rj9ThWDrIo-Ntv6o2D-ckgEuIFw1BiDTOC_1VY2PzHfHrkeUHyP44x9dzbt4aq2T975M2sLsMYU24McdJJ83eTvwsg-ZiN8VtJK8jC2KnZfkjkUsxPp_-eGiGHwq_6S-35PEPgAqSpEc0eUb2gxSkdgVlexWSJzSVAmuVL27LJPw5qDX1reKoPzUdTAa3vSNCpkClRHp5vmA%3D%3D#lns=W251bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLDEsIkVrY0tKRFEwTWpOak56TmpMVGRoTXpBdE5EbGlPQzA0WXpoaUxXWXpPRFJsTVRjeFpEbGhZaElmTUY5Sk9VWTNTSHBXVjAxVlVVVjFlRFl4WHpJd1dFSTRVa2hYY3psNFp3PT0iLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLFtudWxsLG51bGwsW11dXQ==
This search is not NSFW, but the issue may be easier to visualize with a NSFW search since results would be blurred with SafeSearch on.
Description
When searching by image on Google (lens.google.com, or clicking on the camera icon on images.google.com, not a text search on Google Images), explicit images are blurred by default, and there is a notice on top of the search results from which you can change your SafeSearch settings ("Manage" next to "SafeSearch blurring is on"). However, when the "uBlock filters – Cookie Notices" list is enabled, this setting does not work; even if you select "Off," the results are still blurred, and the header says "SafeSearch blurring is on."
I've narrowed it down to this rule:
uAssets/filters/annoyances-cookies.txt
Line 46 in 7441290
Disabling that rule with this custom rule fixes the issue:
Other extensions used
None
Screenshot(s)
Screenshot(s)
SafeSearch turned off:
SafeSearch is still enabled after turning it off and clicking the back arrow (nothing is blurred in this image because none of the results are explicit, but they would be blurred if they were explicit):
Configuration
Details
The text was updated successfully, but these errors were encountered: