-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
♿ AVT 3 ♿ Overflow menu should support links as menu items #1615
Comments
Something I just noticed (in React) In the OverflowMenu, when you have an entry that is an The net is that you end up with an overflow menu where some items are activated via space and some are activated via enter. |
@dakahn So in the case that @lauraalkhoury describes, both link and button should be activated by both space and enter. (So that the user isn't confused). |
Can someone show me an example of where you would have a link instead of an action (button) in the overflow menu? Originally, the overflow menu was only meant for actions (buttons). If there is a good reason to include links then I think we would want to style the links differently than the actions incase they are ever shown together. |
@aagonzales in the case that you want a menu item in your overflow menu to navigate to a new page - for instance, the IBM Cloud Pipeline team has an overflow menu like this: where the "Configure pipeline" item navigates to @dakahn it seems like in carbon-components-react, there was functionality recently added so that when the user adds the
instead of:
So it seems some work has been done to support links as menu items. |
here's the PR for the |
I'll close this since it looks like this functionality has been implemented. Happy to open it up again and continue discussion if we want to though 🏄🏼♂️ |
@dakahn should I open up a separate issue for this problem from my comment above I found in the overflow menu with links vs buttons?
It seems like that is still an issue. |
Absolutely 😸 thank you so so much |
The menu items of an overflow menu could be used for navigation. In this case the user expects to be read a link and not a button. A link element should be supported alongside a button since in the case of navigation it is more semantically correct and in line with user expectation.
Reference
Links vs. Buttons in Modern Web Applications
The text was updated successfully, but these errors were encountered: