Skip to content

Improve top area navigation

What does this MR do?

  1. Changes primary buttons group width on mobile for /dashboard/issues, /dashboard/milestones and /dashboard/merge_requests. This will change width to 100% in order to match similar primary buttons (i.e. /dashboard/groups)
  2. Adds bottom border to support top-area nav-links.
  3. Adds a scrolling container for /dashboard/activity view.

Are there points in the code the reviewer needs to double check?

No but keep in mind that these 3 button groups don't use the latest dropdown toggle already used in /sample-group (introduced in de553961) which already has responsive width and is subtly different in style. We should change all button groups to follow one style.

Why was this MR needed?

To maintain primary button style on mobile (mainly button width).

Screenshots (if relevant)

/dashboard/issues (BEFORE) /dashboard/issues (AFTER)
Issues-BEFORE Issues-AFTER
/dashboard/milestones (BEFORE) /dashboard/milestones (AFTER)
Milestones-BEFORE Milestones-AFTER
/dashboard/merge_requests (BEFORE) /dashboard/merge_requests (AFTER)
MR_BEFORE MR-AFTER
/dashboard/activity (BEFORE) /dashboard/activity (AFTER)
activity_before activity_after

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Review
    • Has been reviewed by UX
    • Has been reviewed by Frontend
Edited by Chris Peressini

Merge request reports