Breadcrumb > Explore small breakpoint behavior
Purpose
Explore a more condensed variant of the breadcrumb at smaller breakpoints so that it can be inline with the nav and right sidebar toggle buttons while still providing intuitive access to the breadcrumb trail.
Concepts
- Truncate all except first and last, truncation expands in place via ellipse button
- Truncate all except first and last, truncation exposed via ellipse dropdown
- First item full
- First item avatar only
- Truncate all except current page, truncation expands in place via ellipse button
- Truncate all except current page, truncation exposed via ellipse dropdown
- Current page as dropdown
- Current page as ellipse button, truncation expands in place
View concepts
Concept | Screenshot | Notes |
---|---|---|
1 | Similar to current desktop experience that uses the ellipse button to hide groups when there are three or more subgroups in the path, only this uses the ellipse button when there are >3 items. | |
2 | Similar to the previous concept, but with a dropdown instead of expand in place. This also explores just using the avatar on the first item. This introduces a problem though where a) it's a small click target, and b) there's no way to see the name unless it's also included in the dropdown, which breaks the pattern of only listing items in between the first and last. There's also the problem of a breadcrumb trail that doesn't start with an item that has an avatar, like this. If the breadcrumb were to expand in place, then the avatar could also expand with the text visible, but this would create an odd jump potentially. | |
3 | A combination of the current expand in place while truncating everything at the front. Like today, this is a one-way action and the breadcrumbs aren't collapsed again until a new page load. | |
4 | Similar to the previous concept, but with a dropdown instead of expand in place. | |
5 | This is the most simplified concept. Since the current page functions as the dropdown trigger, it's repeated in the dropdown as a link and the full breadcrumb trail is present. The slash is visible before the dropdown to provide subtle breadcrumb affordance. | |
6 | Extends the ellipse button with the text of the current page. This seems like the most unconventional of the concepts, and doesn't feel as clear in context. It could also include very long text that would need to be truncated, so then there would be an ellipse icon at the start, and an ellipse character at the end. This concept was included primarily to explore how different components impact the experience and relate to the action. |
Requirements
- Current breadcrumb semantics must remain in place.
- If a dropdown was used, the list of options within should also follow breadcrumb semantics and clearly communicate order.
Examples
Expand in place:
- https://rei.github.io/rei-cedar-docs/components/breadcrumb/#truncated-default
- https://atlassian.design/components/breadcrumbs/examples
- https://www.delldesignsystem.com/components/breadcrumb/?tab=Code#live-demo
Dropdown:
- https://carbondesignsystem.com/components/breadcrumb/style/
- https://elastic.github.io/eui/#/navigation/breadcrumbs
- https://developer.microsoft.com/en-us/fluentui#/controls/web/breadcrumb
- https://spectrum.adobe.com/page/breadcrumbs/#Behaviors
- https://canvas.workday.com/components/navigation/breadcrumbs/#tab=web&heading=overflow-breadcrumbs
Questions
- At what [larger] breakpoint should the truncation and/or behavior change?
- Should the behavior carry through to larger breakpoints?
- Is wrapping allowed?
- How should we proceed with testing?
- Does 128px max width of individual element still apply?
Edited by Jeremy Elder