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
I am developing a blocking webhook to prevent users from changing their usernames. The webhook is functioning correctly, but there's an issue with the UI. Instead of showing the error state in red, it's displaying as green.
Below is the webhook response payload and a screenshot:
The ideal solution would be for the UI to display the blocking webhook response in red, indicating an error or conflict. This would provide a clear visual cue to users that they cannot change their username, aligning with standard UX practices where red typically signifies an error or warning.
Workarounds or alternatives
An alternative could be to keep the UI display as green, indicating success, despite the conflict message. However, this approach is not ideal from a user experience perspective, as it could mislead users into thinking that their action was successful, which could lead to confusion.
Version
0.15.0
Additional Context
Kratos version: v1.2.0
The text was updated successfully, but these errors were encountered:
Preflight checklist
Ory Network Project
No response
Describe your problem
Hello,
I am developing a blocking webhook to prevent users from changing their usernames. The webhook is functioning correctly, but there's an issue with the UI. Instead of showing the error state in red, it's displaying as green.
Below is the webhook response payload and a screenshot:
Thank you !
Describe your ideal solution
The ideal solution would be for the UI to display the blocking webhook response in red, indicating an error or conflict. This would provide a clear visual cue to users that they cannot change their username, aligning with standard UX practices where red typically signifies an error or warning.
Workarounds or alternatives
An alternative could be to keep the UI display as green, indicating success, despite the conflict message. However, this approach is not ideal from a user experience perspective, as it could mislead users into thinking that their action was successful, which could lead to confusion.
Version
0.15.0
Additional Context
Kratos version: v1.2.0
The text was updated successfully, but these errors were encountered: