You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2023. It is now read-only.
I did so, I think, by accidentally double clicking the three dots to bring up the context menu:
The second click of which registered as a click on the first menu option:
Whilst what I describe is user error, it shouldn't be possible IMO to accidentally drain a node just by trying to bring up a context menu. A simple fix here would be to add a spacer to the top of the client-action menu such that when displayed the area above the three-dot button is not a new click handler to actually 'do' something.
The text was updated successfully, but these errors were encountered:
AD7six
changed the title
client three-dot menu
Make client action menu safer to view
Jan 19, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So... I just drained a host unintentionally (:
I did so, I think, by accidentally double clicking the three dots to bring up the context menu:
The second click of which registered as a click on the first menu option:
Whilst what I describe is user error, it shouldn't be possible IMO to accidentally drain a node just by trying to bring up a context menu. A simple fix here would be to add a spacer to the top of the client-action menu such that when displayed the area above the three-dot button is not a new click handler to actually 'do' something.
The text was updated successfully, but these errors were encountered: