-
Notifications
You must be signed in to change notification settings - Fork 827
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(breadcrumbs): Added overflow menu breadcrumb variant
- Loading branch information
1 parent
adb39a6
commit a69621c
Showing
4 changed files
with
78 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -48,4 +48,8 @@ | |
} | ||
} | ||
} | ||
|
||
.slds-dropdown-trigger { | ||
margin-right: $spacing-x-small; | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a69621c
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.
I am curious about whether you were able to determine whether the overflow menu pattern was accessible in breadcrumb interactions? I've been trying something similar, but I'm not sure that it's a good experience for keyboard navigation or assistive technology users.
a69621c
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.
The pattern is plenty accessible, our menus are accessible, our breadcrumbs are accessible, so the 2 together are still "accessible".
Now, is it a good user experience? Is it clear and obvious? Could be debated, but it seems to work well for us when we are constrained by horizontal space and deep hierarchies.
a69621c
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.
Thanks for the reply!
Are you sure? When I tab through the BASE: BREADCRUMBS WITH OVERFLOW MENU example on https://www.lightningdesignsystem.com/components/breadcrumbs/, focus jumps onto Menu Item One as expected, but then skips the other menu items and goes to the PARENT ENTITY breadcrumb. Just because two components are accessible, any particular composition of those components is not necessarily accessible.
Are the docs supposed to include the ability to interact with the components in ways that you would on a production site? I found it really confusing that the breadcrumb overflow menu was just stuck open. I pulled the project down and ran the previewer locally, but I couldn't understand how to use it very well. I would have expected the examples to show the intended interactions that each component supports, not just various states of the component. Am I just missing something?