Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(dropdown): invalid dropdown menu position #4471

Open
wants to merge 3 commits into
base: canary
Choose a base branch
from

Conversation

jijiseong
Copy link

@jijiseong jijiseong commented Dec 31, 2024

Closes #4466

📝 Description

placementProps was converted to PlacementAxis type
using toReactAriaPlacement and useOverlayPosition

// react-aria/overlay

// ...

export type Axis = 'top' | 'bottom' | 'left' | 'right';
export type PlacementAxis = Axis | 'center';

e.g.)
bottom-end -> (toReactAriaPlacement) -> bottom right -> (useOverlayPosition) -> bottom
bottom-start -> (toReactAriaPlacement) -> bottom left -> (useOverlayPosition) -> bottom
top-start -> (toReactAriaPlacement) -> top left -> (useOverlayPosition) -> top

We 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

    • Patched @nextui-org/dropdown dependency
  • Improvements

    • Simplified dropdown positioning logic
    • Removed complex overlay positioning calculations
    • Streamlined dropdown configuration options

Copy link

changeset-bot bot commented Dec 31, 2024

🦋 Changeset detected

Latest commit: b3ffa54

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@nextui-org/dropdown Patch
@nextui-org/react Patch

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

Copy link

vercel bot commented Dec 31, 2024

@jijiseong is attempting to deploy a commit to the NextUI Inc Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Dec 31, 2024

Walkthrough

The 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 use-dropdown.ts file remove previous complex positioning calculations, instead directly using the placementProp for dropdown placement. A patch for the @nextui-org/dropdown dependency is also added, suggesting minor updates to the package.

Changes

File Change Summary
.changeset/silly-hotels-stare.md Added patch for @nextui-org/dropdown dependency
packages/components/dropdown/src/use-dropdown.ts - Removed useOverlayPosition import
- Deleted overlay positioning parameters (containerPadding, offset, etc.)
- Simplified placement logic by directly using placementProp

Assessment against linked issues

Objective Addressed Explanation
Fix Dropdown Arrow Positioning [#4466]
Correct Placement Behavior

Possibly related PRs

Suggested reviewers

  • wingkwong
  • jrgarciadev

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bbef9c8 and b3ffa54.

📒 Files selected for processing (1)
  • .changeset/silly-hotels-stare.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .changeset/silly-hotels-stare.md

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
.changeset/silly-hotels-stare.md (1)

1-6: Changeset reference looks good.
Patching @nextui-org/dropdown and @nextui-org/popover with 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

📥 Commits

Reviewing files that changed from the base of the PR and between d92468a and bbef9c8.

📒 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.

@wingkwong wingkwong added this to the v2.6.11 milestone Dec 31, 2024
Copy link

vercel bot commented Dec 31, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nextui-docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 31, 2024 0:38am
nextui-storybook-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 31, 2024 0:38am

Copy link
Member

@wingkwong wingkwong left a comment

Choose a reason for hiding this comment

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

may double check if the issue occurs in tooltip / popover or not as well

packages/components/popover/src/popover.tsx Outdated Show resolved Hide resolved
.changeset/silly-hotels-stare.md Outdated Show resolved Hide resolved
.changeset/silly-hotels-stare.md Outdated Show resolved Hide resolved
@wingkwong wingkwong requested a review from ryo-manba December 31, 2024 13:03
@jijiseong
Copy link
Author

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.mov
2024-12-31.10.40.43.mov

@jijiseong jijiseong requested a review from wingkwong December 31, 2024 14:26
@jijiseong
Copy link
Author

The Dropdown with arrow case also works well

image

@mohammadshahidbeigh
Copy link

Hi @wingkwong, I'm interested in working on this issue if it's still unresolved. Could you please assign it to me? Thanks!

@jrgarciadev
Copy link
Member

@ryo-manba please confirm if this was also fixed on this PR #4460

@jrgarciadev jrgarciadev removed this from the v2.6.11 milestone Jan 2, 2025
@jijiseong
Copy link
Author

@ryo-manba please confirm if this was also fixed on this PR #4460

PR #4460 is about animation
But this is about DropDown positioning
It is different issue

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.

[BUG] - DropDown arrow position
4 participants