Disable actionable buttons until the actual action can be consumed #493
x80486
started this conversation in
Feature requests
Replies: 2 comments
-
Can i try to solve that? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Go for it! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
This is something that, while a minor detail, could enhance the user experience. Basically, I think that disabling the buttons until the associated action(s) cannot be consumed provide more visual feedback for the users, regardless of their actions within the screen in question.
This enhancement would prevent user confusion and accidental actions, improving the overall usability of the application.
Describe the Solution You Would Like
As an example: when editing a 2FA code, the
Save
button should only be enabled when the code actually changed, compared to the previous value. At the same time, theCancel
button (if any) should always be enabled.Describe Alternatives You Have Considered
N/A
Additional Context
N/A
Beta Was this translation helpful? Give feedback.
All reactions