-
Notifications
You must be signed in to change notification settings - Fork 80
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
matches-path does't work with exception #3235
Comments
How about supporting negation in
|
Isnt't that already possible by |
Yes, you're right. For compatibility with AdGuard, the proper course is to support the same syntax, |
A problem is currently all the |
You can try (I guess in 'uBo – unbreak'): !+ PLATFORM(ext_ublock)
www.nicovideo.jp##:matches-path(/search) body li.item:style(display: list-item !important) If display was not changed by webmaster to not standard. |
Ofc I can fix whatever issues if it is me, but I don't know how other members fix issues. |
If you mean threads that will not reach uAssets or AdGuardFilters (or reddit), the only thing left to do is write something like Wiki in popular place: ! 'search' broken by "##.ads":
!
!#if env_ublock
! disable filter at page in uBo
example.org#@#.ads
! recover in needed places
example.org##:not(:matches-path(/search)) .ads
!#else
[path="search"]example.org#@#.ads
!#endif Due to the number of filters, |
Prerequisites
I tried to reproduce the issue when...
Description
On
https://www.nicovideo.jp/search/%E4%BA%AC%E9%83%BD
These don't work
Using an exception is an official way to handle such cases in AG: AdguardTeam/CoreLibs#124 (comment)
A specific URL where the issue occurs.
https://www.nicovideo.jp/search/%E4%BA%AC%E9%83%BD
Steps to Reproduce
Mentioned
Expected behavior
:matches-path()
should work as well for exception. Preferably ignore whitespace differences:www.nicovideo.jp#@#:matches-path(/search)li.item
andwww.nicovideo.jp#@#:matches-path(/search) li.item
Actual behavior
Mentioned
uBO version
1.57.3b10
Browser name and version
Chrome 124.0.6367.203
Operating System and version
Windows 10
The text was updated successfully, but these errors were encountered: