Plugin Filter Display not working properly #547

Closed
DoomTaper opened this Issue Jan 29, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@DoomTaper
Contributor

DoomTaper commented Jan 29, 2016

On the target list page after clicking on "run" button and then filtering plugins on any basis (lets say on the basis of Name I wrote "http"). Now refresh the page and again click on "run" button, plugins are filtered on "http" basis but it doesn't show "http" in the filter box. Although it doesn't show anything but I have to delete "http" from that filter box to let it show all plugins.

@viyatb viyatb added the Bug label Feb 12, 2016

@viyatb viyatb added this to the OWTF Quality Release milestone Feb 12, 2016

@viyatb viyatb self-assigned this Feb 12, 2016

@viyatb

This comment has been minimized.

Show comment
Hide comment
@viyatb

viyatb Feb 12, 2016

Member

That must be a interface (JS) issue. Can you try changing the behaviour to not persist the search results?

Member

viyatb commented Feb 12, 2016

That must be a interface (JS) issue. Can you try changing the behaviour to not persist the search results?

DoomTaper added a commit to DoomTaper/owtf that referenced this issue Feb 16, 2016

@viyatb

This comment has been minimized.

Show comment
Hide comment
@viyatb

viyatb Feb 20, 2016

Member

After some thought, I don't think that this should be changed. Imagine you want to run some specific plugins and you have already selected a few of them (say 20). Now without stateSave, this selection would not persist an accidental click outside the modal window.
@7a?

Member

viyatb commented Feb 20, 2016

After some thought, I don't think that this should be changed. Imagine you want to run some specific plugins and you have already selected a few of them (say 20). Now without stateSave, this selection would not persist an accidental click outside the modal window.
@7a?

@DoomTaper

This comment has been minimized.

Show comment
Hide comment
@DoomTaper

DoomTaper Feb 20, 2016

Contributor

I think the solution would be to show the user input even after the page reload. @delta24 ?

Contributor

DoomTaper commented Feb 20, 2016

I think the solution would be to show the user input even after the page reload. @delta24 ?

DoomTaper added a commit to DoomTaper/owtf that referenced this issue Feb 20, 2016

@viyatb viyatb closed this in 0dfe229 Feb 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment