Adam
Adam
I think that it can be achieved by using `trusted-set-attr`, for example: ```adblock example.org#%#//scriptlet('trusted-set-attr', 'div', 'class', 'foo bar') ``` Only the `applying` part is not supported, so I guess it...
I think that it's a correct issue. Simple steps to reproduce: 1. Add this rule: ```adblock fiddle.jshell.net#%#//scriptlet('trusted-replace-node-text', 'script', 'alert', '/alert\(\'test\'\)/', 'alert(\'replaced\')') ``` 2. Go to - https://jsfiddle.net/6p7eq9an/ ```html alert('test'); ```...
Also related - https://github.com/AdguardTeam/AdguardFilters/issues/189250#issuecomment-2396540246 (prevented a `new IntersectionObserver` if callback contains `e[0].intersectionRatio` to fix annoying popup).
Here is information about changing origin - https://adguard.com/kb/general/ad-filtering/create-own-filters/#urltransform-modifier:~:text=this%3A%20%5C%2C.-,Changing%20the%20origin,-COMPATIBILITY >As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the...
That's probably related to https://adguard.com/kb/general/ad-filtering/create-own-filters/#cosmetic-rules-priority and website's style has higher priority (specificity) than added rule.
Duplicate of https://github.com/AdguardTeam/AdguardFilters/issues/204916 Please read this comment - https://github.com/AdguardTeam/AdguardFilters/issues/204916#issuecomment-2866285228
> [@Alex-302](https://github.com/Alex-302) Hmm... Somehow the rule `laposte.net$$script:contains(html-load.com)` does not apply on Firefox? > > I think scriptlet cannot inject on time in Firefox, how about using `replace`? > > ||laposte.net^$document,replace=/\(function\(\)\{function[^\n]+html-load\.com[^\n]+?//...
Could you please check this rule: ```adblock ||edgeservices.bing.com/edgesvc/turing/BingChatAdsFetch?showonlyads ``` It seems that it works on my end.
I have checked app only, so I'm not sure, but ads are blocked on web version according to - https://github.com/AdguardTeam/AdguardFilters/issues/182224#issuecomment-2195772664.
I can reproduce it (only in Brave) and it looks like the problem is caused by `$permissions` rules. Even if I add something like `$permissions=whatever=()` then chat is broken, but...