-
Notifications
You must be signed in to change notification settings - Fork 345
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
Specific rules not applied in the new tab on the first opening #2459
Comments
It seems that it's not only about element hide exceptions rules. example.org#%#alert(1); though it seems that for some reasons it's a bit harder to reproduce and doesn't occur as often as issue with exceptions. |
Is it the same as the issue here? 👉 #1772 (comment) If not, please mark it as off-topic. 👍 |
This one is rather a new issue and it probably didn't occur in previous version, I suppose it's not related to mentioned issue. I guess that in the case of #1772 it could have been a race condition and scriptlet was executed too late, but I'm just guessing. |
I observed similar behavior, but in my case I simply refreshed the page and excpetion didn't work. But when I tried to reproduce to report, the trouble dissapeared. |
Actually, I don't know if it's related to this issue or not, but I've seen the similar behaviour on |
AdGuard Extension version
4.2.159
Browser version
Chrome 116
OS version
Windows 11
What filters do you have enabled?
AdGuard Base filter
What Stealth Mode options do you have enabled?
No response
Issue Details
Related to - AdguardTeam/AdguardFilters#160293
It looks like that CSS exceptions do not work after closing and then opening the same website.
Steps to reproduce:
Website is blank, exception rule is not applied.
Video
Recording.2023-08-29.095634.mp4
Expected Behavior
example.org#@#body
should be applied and content should be visible.Screenshots
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: