Skip to content
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

Closed
Fridrix opened this issue Oct 10, 2016 · 10 comments
Closed

Feature request - another filtering log performance. #403

Fridrix opened this issue Oct 10, 2016 · 10 comments
Assignees
Milestone

Comments

@Fridrix
Copy link

Fridrix commented Oct 10, 2016

Adguard users use such steps to watch filtering log:

  • launch a browser
  • go to a website
  • launch a filtering log
  • refresh the page
  • see the requests

We were proposed another guideline to perform it:

  • launch a browser
  • launch a filtering log
  • go to the page
  • see the requests

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.

@ameshkov
Copy link
Member

@Fridrix the second way is also possible, what's the problem with it?

@Fridrix
Copy link
Author

Fridrix commented Oct 10, 2016

@ameshkov its a request of one of the users. He would like to have this feature

@ameshkov
Copy link
Member

@Fridrix I mean this is already possible to use filtering just as user has described.

@Fridrix
Copy link
Author

Fridrix commented Oct 10, 2016

@ameshkov i mean that user could open it even on a blank page
image
Here's no such button

@ameshkov
Copy link
Member

@Fridrix right click on Adguard icon

@Bohdan-SUP
Copy link

Adguard 2.4.14 on Chrome.
That's what I have:

  1. On a blank page:
    image

  2. On some opened page:
    image

@ameshkov ameshkov added this to the 2.5 milestone Oct 11, 2016
@ameshkov
Copy link
Member

Ah, got it, we'll add it to the context menu

@Bohdan-SUP
Copy link

User 1023133 in ticket HGE-951-65974 wonders "Why just add it to the context menu?.....Why not make the filtering log available just like it is on other pages with just simple left click and clicking on search icon"
screen shot 2016-10-12 at 3 20 25 pm

What do you think?

@ameshkov
Copy link
Member

Matter of design I guess. It'd be weird if we show it for a page which we don't filter.

@atropnikov
Copy link
Member

Added to the context menu.

ameshkov added a commit that referenced this issue Feb 10, 2017
…nulog

Feature request - another filtering log performance. #403
maximtop added a commit that referenced this issue Mar 15, 2019
… 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants