Same filters and diff extensions but diff results, why? #24340
-
|
There is no issue if uBO filters are enabled on the uBO side, but why is this so? Thanks in advance. Tested site: Screenshot
Edit: I forgot to disable a filter you see in the picture on the uBO side. I tested again and same result. Screenshot
Update: If i disable EasyList filter too, no issue. But in AdGuard extension, EasyList filter is included in AdGuard Base filter list, how does this happen? Am I missing something? 😄 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 16 replies
-
|
I can't reproduce
Test again in a new browser profile with only uBO and its default settings. |
Beta Was this translation helpful? Give feedback.
-
|
@garry-ut99 Exactly as you said, you explained it perfectly. Thank you. 😄 |
Beta Was this translation helpful? Give feedback.
-
|
I didn't test the case but as said, whether blocking with it unblocked, this one Each of filter list is built upon specific assumption of each blocker and such differences appear also about e.g. |
Beta Was this translation helpful? Give feedback.
-
|
Just in case, I hope the Filter logs from two separate extensions can help. AdGuard Filtering log
uBO Logger output |
Beta Was this translation helpful? Give feedback.
-
|
Regardless of what is the reason of the current specific issue, speaking generally: 100% compatibility all the time between uBO and AG extensions, even when using the same filter list, is not guaranteed, because some filters might be just not 100% compatible, like it's not guaranteed that the same website will work/look 100% same in different browsers (for example: Firefox vs Chrome). |
Beta Was this translation helpful? Give feedback.
-
Your comment is understandable enough. I think there is no need to go deep on this topic then. 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Tested and it's certainly GFC. If you disabled uBf and enabled AG Base, you need |
Beta Was this translation helpful? Give feedback.
-
That filter is already present in Prepending the filter by The reported issue might be caused by internal differences between AdGuard's and uBlock's cosmetic filtering engines: for ex. how soon they inject cosmetic filters, or by some other factors. By the way, alternative ways to fix the AA are:
But these are just alternatives, the point of the case reported by OP is why the anti-adblock message is not hidden by filtes which are already present on |
Beta Was this translation helpful? Give feedback.
-
|
It's not "earlier", uBO doesn't support generic css filter without |
Beta Was this translation helpful? Give feedback.
Regardless of what is the reason of the current specific issue,
speaking generally: 100% compatibility all the time between uBO and AG extensions, even when using the same filter list, is not guaranteed, because some filters might be just not 100% compatible, like it's not guaranteed that the same website will work/look 100% same in different browsers (for example: Firefox vs Chrome).