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

New skip dropdown in notification window slows down the process of filtering blocked connections #131

Open
esrat opened this issue Feb 20, 2021 · 1 comment

Comments

@esrat
Copy link

esrat commented Feb 20, 2021

The seperate skip buttons of previous versions (I saw them at least with nightly builds in 2020.) were more conveniently to use, especially when there was a longer list of blocked events.
No matter if the user wanted to skip only one event, a whole application or all blocked events to maybe start some configuration with an empty history, these were all done by just one single click. Now every single use case needs two clicks (with additional animation time, see #128).

This should not be a competition for shrinking the notification window to its minimal size. Other firewalls are showing more options and information, too. There is no space problem with today's screen sizes, at least when you can put the window where you want it to stay, see #129.

@esrat
Copy link
Author

esrat commented Feb 21, 2021

I have to revoke this issue partly.
Ich had to wait until new blocked events came in to see the new functionality once more (due to some animation related accident, see #128). Now I see that the skip drop down at least stays open which helps if the user only wants to skip events. For every rule action in between, this still means additional clicks (as well as hidden window space while the drop down is open where there is no need of this).
As a little additional bug, the drop down stays open after the last event was skipped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant