-
Notifications
You must be signed in to change notification settings - Fork 4k
Fix dropdown overlay not staying fixed #3164
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: d980d7a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
Summary of the deployments: Version 1
Version 2
Test content |
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
/** Whether to use fixed positioning (for fixed navbars) */ | ||
useFixedPosition?: boolean; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure to understand why we need a special prop for this. The default behaviour of the dropdown is it's fixed and anchored to it's parent no matter what the situation is. Exposing a prop like this leaks implementation details that is not very clear for the caller of this API
This is meant to be a quick fix to solve a bug. We should probably move to a more properly supported Dropdown element like react-aria or Radix. But this works for now.
Before
CleanShot.2025-04-15.at.16.56.54.mp4
After
CleanShot.2025-04-15.at.16.57.29.mp4