Skip to content

Add menu support to folder-contents breadcrumb for long navigation titles#7640

Draft
iFlameing wants to merge 4 commits intomainfrom
breadcrumbs-long-title
Draft

Add menu support to folder-contents breadcrumb for long navigation titles#7640
iFlameing wants to merge 4 commits intomainfrom
breadcrumbs-long-title

Conversation

@iFlameing
Copy link
Member

… title

Caution

The Volto Team has suspended its review of new pull requests from first-time contributors until the release of Plone 7, which is preliminarily scheduled for the second quarter of 2026.
Read details.



If your pull request closes an open issue, include the exact text below, immediately followed by the issue number. When your pull request gets merged, then that issue will close automatically.

Closes #


If your pull request includes changes to the documentation—either in narrative documentation, Storybook, or configuration—then a pull request preview will be generated and a link will populate in the description of your pull request below.
By clicking that link, you can use the visual diff menu in the upper right corner to navigate to pages that have changes, then display the diff by checking the Show diff checkbox.

@iFlameing
Copy link
Member Author

@sneridagh can you please review if I am doing everything right? we need talk about the css changes.

screenshot

@iFlameing iFlameing marked this pull request as draft November 19, 2025 14:12
@iFlameing iFlameing changed the title Add menu opening in folder-contents-breadcrumb due to long navigation… Add menu support to folder-contents breadcrumb for long navigation titles Nov 19, 2025
Copy link
Member

@sneridagh sneridagh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM so far!


const navigate = (to, options = {}) => {
if (options.replace) {
history.replace(to);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this condition for?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To support replace instead of push behaviour.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in Link of react-aria-component you can pass options like replace and I want to support it that's why.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it actually used by the breadcrumbs? If not it should be in its own PR with its own entry in the release notes.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@davisagli Yes, if we don’t implement it in this PR, then folder-content navigation will not work.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you see the pr I have added the routercontext so that client side navigation work for Link components of react-aria-components.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iFlameing Please add an entry of its own in this PR mentioning the new provider and what's for, I think the change is worth the effort.

@iFlameing
Copy link
Member Author

I am busy, that's why I am not working on this. I will update it as soon as i get time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants