Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D design
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Primer
  • design
  • Issues
  • #290
Closed
Open
Issue created Sep 09, 2022 by Maxime De Greve@maximedegreveContributor

Improve cancel button guidelines

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:

  • Should a cancel button be used on intermediate form pages (not just modals)
  • Cancelling can be useful when by accident changing the form
  • Are there accessibility considerations here?

Original Slack thread (internal)

Assignee
Assign to
Time tracking