-
Notifications
You must be signed in to change notification settings - Fork 56
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
Docs > Component > Nav-tabs: change place of dropdown menu #2007
Docs > Component > Nav-tabs: change place of dropdown menu #2007
Conversation
Signed-off-by: Isabelle Chanclou <isabelle.chanclou@orange.com>
✅ Deploy Preview for boosted ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok for the code.
But I am not sure if the design can really prevail over the functionnality in this particular case. Any application may need to have a dropdown elsewhere than in the last position.
And if this is truly the rule then the rule must be clearly written somewhere.
Signed-off-by: Isabelle Chanclou <isabelle.chanclou@orange.com>
Signed-off-by: Isabelle Chanclou <isabelle.chanclou@orange.com>
Decided in daily meeting (on April 24th 2023): ask the design for a sentence that explains why the dropdown nav-item should be at the end of the list and not elsewhere. This sentence is to be added above the concerned examples and in a design-callout-info message. |
This comment was marked as resolved.
This comment was marked as resolved.
Kudos, SonarCloud Quality Gate passed! |
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Just added an info callout to precise the design recommendation which could help projects without designers. There are use cases where it's not true IMHO so I've just carefully explained the rule with words like "typically" and "recommendation".
It can be revisited later if we have a more precise rule coming from the designers (that should be mentioned in the DSM).
No need to add a migration note since it's a pure design recommendation for edge cases in our documentation or in projects.
Note: Please transform
- [ ]
into- (NA)
in the description when things are not applicableRelated issues
#1811
Description
In #using-dropdowns dans #pills-with-dropdowns sections, the dropdown menu shall be the last item in the list and therefore placed at the end of the list.
Motivation & Context
Modification asked by design when working on the design callout messages to make this variant compliant with the Orange design system.
Types of change
Live previews
Checklist
Contribution
Accessibility
Design
Development
Documentation
Checklist (for Core Team only)
After the merge