-
Notifications
You must be signed in to change notification settings - Fork 25
fix(navigation primary): secondary items fit content at #2405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
fix(navigation primary): secondary items fit content at #2405
Conversation
|
✅ Deploy Preview for red-hat-design-system ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Size Change: +238 B (+0.1%) Total Size: 231 kB
ℹ️ View Unchanged
|
Can we do this with CSS only? Adding SSR complexity to this element specifically is likely to have downstream implications. This also subtly breaks the already accepted designs, so we shouldn't add this feature in any regard, without design and PM input. |
I'm not sure we should do it at all. I agree with it breaking the accepted designs, and would prefer these changes be formally requested by design first if there is an issue with the component as is. For these reasons, the PR remains in draft. I added the "hold" status to it. This was in response to a "bug/can we have" report by the RHDC team, but upon reviewing the details and the design originally provided, I'm not convinced yet either. |
What I did
menu-fit-content-at
attributes. Allows secondary items to change when they move from mobile full-screen tofit-content
widthTODO:
compact
(padding changes) and these new breakpointsstaging/diglett
due to this change being aminor
hide-at.
Breaking? If so, we may want to revert that commit and open an issue for the change on the next available major.Testing Instructions
Notes to Reviewers
ts.