feat(GlButton): remove BButton from GlButton

Peter Hegmanrequested to merge
3163-remove-bbutton-from-glbutton into main

What does this MR do?

Closes #3163 (closed)

Removes BButton from GlButton. Part of a larger migration to remove Bootstrap Vue dependency from GitLab UI.

This is a breaking change that removes support for the following props:

  • pressed - we do not use this prop in any projects

Router props

These props were dropped when removing BLink from GlLink in !4889 (merged) because we do not use them in our projects and support for them is removed in Vue Router 4 (for Vue 3).

  • router-component-name
  • exact
  • exact-path
  • exact-path-active-class (replaced with exact-active-class)
  • no-prefetch (use prefetch instead)

Screenshots or screen recordings

Integration merge requests

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • [-] If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • [-] If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • [-] Label as security and @ mention @gitlab-com/gl-security/appsec
  • [-] Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.
Edited by Peter Hegman

Merge request reports