-
Notifications
You must be signed in to change notification settings - Fork 235
feat(action-bar): support for action-menus #3780
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
Conversation
Tachometer resultsChromeaccordion permalink
action-bar permalink
action-button permalink
action-group permalink
action-menu permalink
alert-dialog permalink
avatar permalink
badge permalink
button-group permalink
button permalink
card permalink
checkbox permalink
color-area permalink
color-slider permalink
color-wheel permalink
dialog permalink
field-label permalink
grid permalink
infield-button permalink
link permalink
menu permalink
meter permalink
number-field permalink
overlay permalink
picker-button permalink
picker permalink
popover permalink
progress-bar permalink
progress-circle permalink
radio permalink
search permalink
sidenav permalink
slider permalink
split-button permalink
swatch permalink
switch permalink
table permalink
tabs permalink
tags permalink
textfield permalink
toast permalink
tooltip permalink
top-nav permalink
tray permalink
Firefoxaccordion permalink
action-bar permalink
action-button permalink
action-group permalink
action-menu permalink
alert-dialog permalink
avatar permalink
badge permalink
button-group permalink
button permalink
card permalink
checkbox permalink
color-area permalink
color-slider permalink
color-wheel permalink
dialog permalink
field-label permalink
grid permalink
infield-button permalink
link permalink
menu permalink
meter permalink
number-field permalink
overlay permalink
picker-button permalink
picker permalink
popover permalink
progress-bar permalink
progress-circle permalink
radio permalink
search permalink
sidenav permalink
slider permalink
split-button permalink
swatch permalink
switch permalink
table permalink
tabs permalink
tags permalink
textfield permalink
toast permalink
tooltip permalink
top-nav permalink
tray permalink
|
87ef5ab to
c6e1604
Compare
najikahalsema
left a comment
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.
Any clue why these VRTs are changing? That seems unexpected to me. I'm fine with the background changing since I believe that is supposed to match the other action buttons in the action group, but I'm curious about the corners being unrounded. Here's a link to the story in your branch and a link to what's live now.
Also, in order to make sure the addition of the action menu to the ActionBar stories is captured by the VRTs, can you add one extra story that's called "With Action Menu" or something, and have that story start with the ActionMenu in an open state?
Please investigate why the tests are failing. Looks like there's some accessibility issues that need addressing. I think it'd be good to add some tests. Generally, we want to add tests for every new feature we add to a component. A place to start... I did notice that the tab order is broken in your PR in the stories I linked previously, because I can't tab into the action group before the action menu. It also doesn't work as expected in the ActionBar's default story. Some stories regarding this tab index behaviour are probably a good thing to cover in the test file.
Westbrook
left a comment
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.
NOTE: for this to be accurately supported in Action Bar, it needs to be accurately supported in Action Groups. Not only does it need to accept the size, static, etc. attribute from the Action Group, but it should play as expected into the keyboard interaction model of the group as well.
0439ba0 to
301cac6
Compare
1c5b0ea to
92d6693
Compare
92d6693 to
27723e1
Compare
|
In https://feat-action-menu-in-action-bar--spectrum-web-components.netlify.app/storybook/?path=/story/action-bar--default when I navigate to the Action Menu with the keyboard, I am unable to access any of the Menu Items once it is opened. |
1756fd2 to
dc2936d
Compare
nikkimk
left a comment
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.
Action Menu is not focusable via keyboard within action menu:
- Go to https://feat-action-menu-in-action-bar--spectrum-web-components.netlify.app/storybook/?path=/story/action-bar--fixed
- Navigate to the action bar via keyboard, so that the Close button has focus.
- Press Tab, so that the Edit button has focus.
- Press Tab again, and the More action menu should have focus, but instead focus is moved outside of the action bar to the System Picker after it.
|
@nikkimk This is an expected behaviour as we've placed the edit button and the action-menu in the action-group so you should be able to use arrow keys to navigate between the two items inside of the action-group but using tab will jump to the next focusable element which in this case is the picker. |
|
Here's the attached documentation for these changes. |
|
@Rajdeepc I have addressed all the comments on the PR. Please take a look. |
blunteshwar
left a comment
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❗
|
LGTM |
Description
Action Menu is not currently an accepted child of Action Bar. Expanding the Action Group management that is internally leveraged by Action Bar to include Action Menu would enable clients to use Action Menu with slot "buttons" and may also help resolve the Menu overlay overlap issue.
Related issue(s)
Motivation and context
How has this been tested?
Screenshots (if appropriate)
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main.