We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Our saving docs is already doing a great job at providing guidelines but on when to use cancel button and when not.
One relevant bit on saving is: When data is not automatically saved after the user makes changes, buttons are used to submit or cancel the changes.
When data is not automatically saved after the user makes changes, buttons are used to submit or cancel the changes.
This might imply we should always include a cancel button but that isn't correct. For example on a login page this won't be useful.
Considerations:
cancel
Original Slack thread (internal)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Our saving docs is already doing a great job at providing guidelines but on when to use cancel button and when not.
One relevant bit on saving is:
When data is not automatically saved after the user makes changes, buttons are used to submit or cancel the changes.
This might imply we should always include a cancel button but that isn't correct. For example on a login page this won't be useful.
Considerations:
cancel
button be used on intermediate form pages (not just modals)Original Slack thread (internal)
The text was updated successfully, but these errors were encountered: