feat(merge request reports): Replace modal with drawer
What does this MR do?
This MR updates the merge request reports guidance to use drawers instead of modals if using inline links. When looking at the modal component guidance, we are not supposed to use modals to show additional content When content can be displayed inline. Utilize elements such as popovers, accordions, or drawers to present additional information while allowing the user to maintain focus on the page.
With the new work that Code Quality gitlab-org/gitlab#388258 (closed)Code_quality_-inline_findings-expanded-_cq_detail_drawer.png is working on for enhancing the code quality MR widget, and with the direction that UX is going for future MR reports gitlab-org/gitlab#389441 (closed), we should always use drawers if additional content is necessary from inline elements in an MR widget.
Does this MR meet the acceptance criteria?
-
The MR title and commit messages meet the Pajamas commit conventions. -
The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per “Say why not just what”. - For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
-
Relevant label(s) are applied to the MR. -
The MR is added to a milestone. -
If creating a new component page from scratch, it follows the page template structure. -
Content follows the Pajamas voice and tone guidelines, falling back on the GitLab Documentation Style Guide when needed. -
Related pages are cross-linked, where helpful. Component pages have related components and patterns defined in their Markdown front matter. -
If embedding a Figma file, it follows the Figma embed guide. -
Review requested from any GitLab designer or directly from a maintainer or trainee maintainer.