-
Notifications
You must be signed in to change notification settings - Fork 5
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
Implement OnyxFlyoutMenu #883
Comments
As discussed, this would be our prefered API for the nav bar: <template>
<OnyxNavBar>
<OnyxNavButton>
Item 1
<OnyxBadge dot />
</OnyxNavButton>
<OnyxNavButton>
Item 2
<template #children>
<OnyxNavItem> I am child 1 </OnyxNavItem>
<OnyxNavItem> I am child 2 </OnyxNavItem>
<OnyxNavItem> I am child 3 </OnyxNavItem>
</template>
</OnyxNavButton>
<OnyxUserMenu>
<OnyxListItem @click="handleLogout">
<OnyxIcon />
Logout
</OnyxListItem>
<OnyxListItem @click="router.push('/settings')"> Settings </OnyxListItem>
</OnyxUserMenu>
</OnyxNavBar>
</template> |
This was referenced Jun 3, 2024
2 tasks
This was referenced Jun 11, 2024
MajaZarkova
added a commit
that referenced
this issue
Jun 19, 2024
<!-- Is your PR related to an issue? Then please link it via the "Relates to #" below. Else, remove it. --> Relates to #883 Implement onyx nav button ## Checklist - [x] If a new component is added, at least one [Playwright screenshot test](https://github.com/SchwarzIT/onyx/actions/workflows/playwright-screenshots.yml) is added - [x] A changeset is added with `npx changeset add` if your changes should be released as npm package (because they affect the library usage) --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2 tasks
MajaZarkova
added a commit
that referenced
this issue
Jun 27, 2024
<!-- Is your PR related to an issue? Then please link it via the "Relates to #" below. Else, remove it. --> Relates to #883 <!-- Briefly describe the changes of this PR. --> Implemented new OnyxNavItem component which is similar to OnyxListItem, but will be used in OnyxNavButton only. ## Checklist - [x] If a new component is added, at least one [Playwright screenshot test](https://github.com/SchwarzIT/onyx/actions/workflows/playwright-screenshots.yml) is added - [x] A changeset is added with `npx changeset add` if your changes should be released as npm package (because they affect the library usage) --------- Co-authored-by: Linda Bopp <[email protected]> Co-authored-by: Jonathan Carle <[email protected]>
larsrickert
pushed a commit
that referenced
this issue
Jul 16, 2024
Relates to #1415, #883 Closes #1518 - implemented headless feature: `createNavigationMenu` - headless MenuButton: - now takes an `isExpandedRef` and `onToggle` via it's options - `flyout` element is removed as it is not needed - removed hover and focus toggle features and moved them to the onyx component directly as these are non spec features
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Open Questions/To-dos
Why?
This component is needed and will be used inside the NavMenuItem. This is just a support component.
It's responsible for handling keyboard navigation, rendering and opening of the flyout.
Design
Figma Link (Context Area section)
Acceptance criteria
Definition of Done
In Approval
Approval
- OnyxNavButton will replace OnyxNavItem. OnyxNavItem is re-written and it's actually used inside OnyxNavButton
Reference implementations
CoreUI Reference
ARIA
https://www.w3.org/WAI/ARIA/apg/patterns/menubar/examples/menubar-navigation/
https://www.w3.org/WAI/ARIA/apg/patterns/menu-button/
https://www.w3.org/WAI/ARIA/apg/patterns/disclosure/examples/disclosure-navigation/
https://www.w3.org/WAI/ARIA/apg/patterns/menubar/
The text was updated successfully, but these errors were encountered: