-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Labels
Status: Needs TriageIssue will be reviewed by Core Team and a relevant label will be added as soon as possibleIssue will be reviewed by Core Team and a relevant label will be added as soon as possible
Description
Describe the bug
Description
This is a simplified version of my component:
<Menu>
<Menu.Trigger>
<span>Menu</span>
</Menu.Trigger>
<Menu.Portal>
<Menu.List>
<Menu.Item as={NextLink} href="/">
Home
</Menu.Item>
<Menu.Item as={NextLink} href="/about">
About
</Menu.Item>
</Menu.List>
</Menu.Portal>
</Menu>When using the Menu component with Menu.Portal and Menu.Item rendered as link (as={NextLink}), clicking the menu item closes the dropdown without triggering the actual navigation to the href.
Environment
- PrimeReact: 11.0.0-alpha.9
- React: 19.2.0
- Next.js: 15.5.9
- Tailwindcss: 4.1.17
Suspected Cause
It appears the click event handler that closes the Portal is preventing the default link behavior or stopping event propagation before the NextLink can trigger its navigation. The event sequence seems to prioritize closing the Portal over following the href.
Reproducer
No response
System Information
System:
OS: Windows 11 10.0.26200
CPU: (22) x64 Intel(R) Core(TM) Ultra 7 165H
Memory: 10.30 GB / 31.46 GB
Binaries:
Node: 23.10.0 - C:\nvm4w\nodejs\node.EXE
npm: 10.9.2 - C:\nvm4w\nodejs\npm.CMD
Browsers:
Chrome: 143.0.7499.147
Edge: Chromium (140.0.3485.54)
Firefox: 141.0 - C:\Program Files\Mozilla Firefox\firefox.exeSteps to reproduce the behavior
See code snippet
Expected behavior
No response
Metadata
Metadata
Assignees
Labels
Status: Needs TriageIssue will be reviewed by Core Team and a relevant label will be added as soon as possibleIssue will be reviewed by Core Team and a relevant label will be added as soon as possible