Skip to content
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

Merged
merged 6 commits into from
Jul 28, 2023

Conversation

isabellechanclou
Copy link
Member

@isabellechanclou isabellechanclou commented Apr 21, 2023

Note: Please transform - [ ] into - (NA) in the description when things are not applicable

Related 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

  • Bug fix (non-breaking which fixes an issue)

Live previews

Checklist

Contribution

Accessibility

  • My change follows accessibility good practices; I have at least run axe

Design

  • My change respects the design guidelines defined in Orange Design System
  • My change is compatible with responsive display

Development

  • My change follows the developer guide
  • I have added JavaScript unit tests to cover my changes
  • I have added SCSS unit tests to cover my changes

Documentation

  • My change introduces changes to the documentation and/or I have updated the documentation accordingly

Checklist (for Core Team only)

  • My change introduces changes to the migration guide
  • My new component is added in Storybook
  • My new component is compatible with RTL
  • Manually run BrowserStack tests
  • Manually test browser compatibility with BrowserStack (Chrome >= 60, Firefox >= 60 (+ ESR), Edge, Safari >= 12, iOS Safari, Chrome & Firefox on Android)
  • Code review
  • Design review
  • A11y review

After the merge

Signed-off-by: Isabelle Chanclou <isabelle.chanclou@orange.com>
@isabellechanclou isabellechanclou added v5 docs Improvements or additions to documentation enhancement labels Apr 21, 2023
@isabellechanclou isabellechanclou self-assigned this Apr 21, 2023
@netlify
Copy link

netlify bot commented Apr 21, 2023

Deploy Preview for boosted ready!

Name Link
🔨 Latest commit f833cbf
🔍 Latest deploy log https://app.netlify.com/sites/boosted/deploys/64c36d99d6a20a0008812ffd
😎 Deploy Preview https://deploy-preview-2007--boosted.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@isabellechanclou isabellechanclou linked an issue Apr 21, 2023 that may be closed by this pull request
3 tasks
@MewenLeHo MewenLeHo self-requested a review April 24, 2023 06:39
Copy link
Contributor

@MewenLeHo MewenLeHo left a 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>
@isabellechanclou
Copy link
Member Author

isabellechanclou commented Apr 26, 2023

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.

MewenLeHo

This comment was marked as outdated.

@julien-deramond

This comment was marked as resolved.

@sonarcloud
Copy link

sonarcloud bot commented Apr 26, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@MewenLeHo

This comment was marked as resolved.

@julien-deramond julien-deramond self-requested a review July 28, 2023 07:12
Copy link
Member

@julien-deramond julien-deramond left a 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.

@julien-deramond julien-deramond merged commit a669275 into main Jul 28, 2023
12 checks passed
@julien-deramond julien-deramond deleted the main-ic-fix-nav-tabs-dropdown-menu-place branch July 28, 2023 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation enhancement v5
Projects
Development

Successfully merging this pull request may close these issues.

Docs > Component > Nav-tabs > #using-dropdowns: Fix dropdown menu place
3 participants