mirror of
https://github.com/laylavish/uBlockOrigin-HUGE-AI-Blocklist.git
synced 2026-08-06 02:12:35 -04:00
[GH-ISSUE #148] Filter blocks all image search results on Duckduckgo #84
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: DYNR/uBlockOrigin-HUGE-AI-Blocklist#84
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CinderBH on GitHub (Apr 10, 2025).
Original GitHub issue: https://github.com/laylavish/uBlockOrigin-HUGE-AI-Blocklist/issues/148
Used via uBO, this filter often (but not always) blocks ALL image search results in Duckduckgo. Issue observed in Firefox 137.
@itsasooz commented on GitHub (Apr 13, 2025):
Have the same problem, not 100% consistent:
The problem seems to be with showing images and text, as the links still seem to function. Outgoing links work as normal; the image feature links seem to open the feature, but I can't tell because no text or images.
I'm on Firefox 137.0.1, UBO 1.63.2 with everything updated. Have confirmed that the issue is caused by this particular filter.
@CEa-TIde commented on GitHub (Apr 26, 2025):
On Firefox 137.0.1, uBO 1.63.2, list updated.
Why it happens
This happens when any of the ai sites show up in the results (with a link).
In the case in the image below the following filter was triggered:
google.com,duckduckgo.com,bing.com##a[href*="forkful.ai"]:upward(div):style(opacity:0.00!important;)(it is the first filter in this case)
The problem arises when evaluating
:upward(div). None of the elements you want to filter aredivs, so it continues until it finds the container for all images.How to reproduce:
forkful.ai)Potential fix
You would want to filter the first
lielement it finds upward instead.[...]:upward(li):style(...)would do that, but since you're also targeting google.com and bing.com, a different rule might be needed, or in the worst case even separate rules for each.@khatharsis42 commented on GitHub (Apr 28, 2025):
Please fix this, it's... really annyoing
@ReedGraf commented on GitHub (Apr 28, 2025):
I also am experiencing this issue and can confirm it happens irregularly.
@laylavish commented on GitHub (Apr 30, 2025):
Okay, try it now. Working fine on my end.
@CEa-TIde commented on GitHub (Apr 30, 2025):
Also working on my end on duckduckgo, and did a quick check on bing/google as well.
@ReedGraf commented on GitHub (Apr 30, 2025):
Also working for me now. 👍
Thanks!
@laylavish commented on GitHub (Apr 30, 2025):
Cool. Got two confirmations that it's working, closing this issue now.