fix(dropdown): invalid dropdown menu position#4471
Conversation
🦋 Changeset detectedLatest commit: b3ffa54 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@jijiseong is attempting to deploy a commit to the NextUI Inc Team on Vercel. A member of the Team first needs to authorize it. |
WalkthroughThe pull request introduces changes to the dropdown component's positioning logic by removing overlay-related imports and simplifying the placement configuration. The modifications in the Changes
Assessment against linked issues
Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
.changeset/silly-hotels-stare.md (1)
1-6: Changeset reference looks good.
Patching@nextui-org/dropdownand@nextui-org/popoverwith a brief note describing the removal of the conversion logic is concise and clear. Consider adding a reference to the PR or the issue number (#4466) to provide further context for maintainers and collaborators.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
.changeset/silly-hotels-stare.md(1 hunks)packages/components/dropdown/src/use-dropdown.ts(2 hunks)packages/components/popover/src/popover.tsx(0 hunks)
💤 Files with no reviewable changes (1)
- packages/components/popover/src/popover.tsx
🔇 Additional comments (2)
packages/components/dropdown/src/use-dropdown.ts (2)
12-12: Confirm usage of ariaShouldCloseOnInteractOutside is fully compatible with your existing logic.
It's great to see the usage of ariaShouldCloseOnInteractOutside for controlling interactions outside the dropdown. Ensure that its return behavior aligns with all desired edge cases, such as when nested elements or extended custom triggers are used.
151-151: Placement is now derived directly from placementProp.
Removing the intermediate logic significantly simplifies the code. However, verify that passing any advanced values (e.g., bottom-end) is correctly handled by the underlying popover logic.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
wingkwong
left a comment
There was a problem hiding this comment.
may double check if the issue occurs in tooltip / popover or not as well
tooltip and popover work well 2024-12-31.10.44.47.mov2024-12-31.10.40.43.mov |
|
Hi @wingkwong, I'm interested in working on this issue if it's still unresolved. Could you please assign it to me? Thanks! |
|
@ryo-manba please confirm if this was also fixed on this PR #4460 |
PR #4460 is about animation |
|
I checked with Storybook and there seems to be an animation problem. |
|
Hi @jijiseong, Thank you for creating the PR! |

Closes #4466
📝 Description
placementProps was converted to
PlacementAxistypeusing
toReactAriaPlacementanduseOverlayPositionWe want use the original placement instead of converting it to PlacementAxis.
So I delete the conversion logic.
⛳️ Current behavior (updates)
2024-12-31.8.38.22.mov
🚀 New behavior
2024-12-31.8.40.14.mov
💣 Is this a breaking change (Yes/No):
📝 Additional Information
Summary by CodeRabbit
Dependency Update
@nextui-org/dropdowndependencyImprovements