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
Feature request - another filtering log performance. #403
Comments
@Fridrix the second way is also possible, what's the problem with it? |
@ameshkov its a request of one of the users. He would like to have this feature |
@Fridrix I mean this is already possible to use filtering just as user has described. |
@ameshkov i mean that user could open it even on a blank page |
@Fridrix right click on Adguard icon |
Ah, got it, we'll add it to the context menu |
Matter of design I guess. It'd be weird if we show it for a page which we don't filter. |
Added to the context menu. |
…nulog Feature request - another filtering log performance. #403
… to master * commit '7ac6856855f3666bd037149d7a82a6c6f76d233b': fix/1315 correct error for the firefox 52 fix/1315 revert popup-controller.js fix/1315 fix forEach method for the nodeElements fix/1315 fix/1315 remove comma which was cause of unexpected token error in the chrome 56
Adguard users use such steps to watch filtering log:
We were proposed another guideline to perform it:
The main thing is that user could open filtering log through Adguard extension or Assistant icon even on blank new tab page and could watch work of Adguard filters in real-time mode.
The text was updated successfully, but these errors were encountered: