feat(design)!: update breadcrumb component to support truncation#3569
Closed
feat(design)!: update breadcrumb component to support truncation#3569
Conversation
Member
Author
|
via css:
Proposed new usage: Last breadcrumb item should not be clickable/linked. Last breadcrumb item should have the class |
74e7476 to
2ff15ba
Compare
Member
Author
Contributor
|
@xelaint @damienwebdev Hey, I've resolved the bug where the ellipses to open the menu doesn't always work, as well as the issue where the item at index 2 is not in the partial menu. May I ask if there were any additional errors that were identified when this draft PR was created? |
15 tasks
Member
Author
|
Closed in favor of #4278 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Fixes: #3513
What is the new behavior?
Does this PR introduce a breaking change?
Other information