-
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
YouTube detects Adguard and makes notification/unsubscribe control buttons invisible #2575
Comments
Reproduced with all options turned off and paused AdGuard. |
@evd316 Это не вопрос и не решение. Человек говорит, что у него повторилась проблема со всеми отключенными опциями и расширением на паузе. |
@alexx7311 |
@Chilace You may also test when the option in the message above is disabled. |
@Alex-302 |
On my end the button is broken with opened filtering log. |
Same here |
This issue still doesn't seem to be solved. None of the methods mentioned above are available. |
Turning off "Help with the development of AdGuard filters" and then restarting my chrome browser worked for me, sad that Youtube and Google may be hindering the progress of Ad blocker developers. |
AdGuard Extension version
4.2.209 beta
Browser version
Chrome 119, Edge 118
OS version
Windows 10 22H2
What filters do you have enabled?
No response
What Stealth Mode options do you have enabled?
No response
Issue Details
Some time ago I noticed that I could not turn off notifications/unsubscribe from a channel - there was no button for this.
The button has disappeared from both the channel page and the subscription management page.
On channels to which I am not subscribed, the subscribe button is present, but disappears as soon as I click it (subscribe).
What I tried to do:
Nothing helps except two things:
Expected Behavior
Subscription management buttons should not disappear
Screenshots
Disappearing button:
Dev tools:
Additional Information
Don't pay attention to the fact that the GIF shows that extensions and filtering are enabled.
I recorded it a couple of days after the tests just for demonstration purposes
The text was updated successfully, but these errors were encountered: