-
Notifications
You must be signed in to change notification settings - Fork 72
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
Menu point "block request" (filter protocol) don't work #5201
Comments
@Summerjay1893 Hi, Could you say which version of AdGuard you use? Have you tried the latest Nightly build? Cannot be reproduced on my side. |
Could you also send us a short video of this problem? |
I have tried the latest stable version and the latest nightly build. |
Omg, i'm so stupid man, sorry. I expected that a configuration menue appears (that was my wrong memory of this function) if i click one block request. But i must make a double click on the entry and then the suggested rules appears in the right half of the windows. |
It turns out the button in the context menu doesn't work if the sidebar isn't open, so there is a problem Videoup85_zxqi3.mp4 |
It is possible to make this function more comfortable? For Example over an menu entry in the adguard assistant maybe? |
Please answer the following questions for yourself before submitting an issue
AdGuard version
Latest stable Version
Browser version
latest stable versions from Chrome and Firefox
OS version
Windows 11 23H2 (22631.3958)
Traffic filtering
Ad Blocking
AdGuard Base filter
Privacy
No response
Social
No response
Annoyances
AdGuard Annoyances filter
Security
No response
Other
No response
Language-specific
AdGuard German filter
Which DNS server do you use?
DNS protection disabled
DNS protocol
None
Custom DNS
No response
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
Steps to reproduce:
Expected Behavior
i expected that a configuration mask appears, but nothing happens.
Actual Behavior
If i want to go the menu point "block request" from an entry in the filterprotocol nothing happens.
Screenshots
Screenshot 1
Additional Information
No response
The text was updated successfully, but these errors were encountered: