Skip to content

Replace btn-transparent with equivalent util classes

What does this MR do and why?

This MR replaces the use of btn-transparent with the relevant util classes as per the strategy outlined in the epic attached to the issue: &15370

No visual changed expected.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After
Screenshot_2024-10-01_at_15.11.35 Screenshot_2024-10-01_at_15.11.35

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Visit an issue and upload a design to it.
  2. Click on the design and add some comments.
  3. Visit the work item equivalent to that issue.
  4. Click on a design to open it.
  5. Verify the pins display properly and highlight the corresponding discussion on click.
  • Issue example URL: http://127.0.0.1:3000/gitlab-org/gitlab-shell/-/issues/2
  • Corresponding work item URL: http://127.0.0.1:3000/gitlab-org/gitlab-shell/-/work_items/2

Related to #496555 (closed)

Edited by James Rushford

Merge request reports

Loading