Skip to content

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

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

Conversation

zenoachtig
Copy link
Contributor

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

Copy link

changeset-bot bot commented Apr 15, 2025

🦋 Changeset detected

Latest commit: d980d7a

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

This PR includes changesets to release 1 package
Name Type
gitbook 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

argos-ci bot commented Apr 15, 2025

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build Status Details Updated (UTC)
customers-v1 (Inspect) ⚠️ Changes detected (Review) 4 changed Apr 15, 2025, 3:06 PM
customers-v2 (Inspect) ⚠️ Changes detected (Review) 4 changed Apr 15, 2025, 3:06 PM
default (Inspect) ⚠️ Changes detected (Review) 3 changed Apr 15, 2025, 3:10 PM
v2-vercel (Inspect) ✅ No changes detected - Apr 15, 2025, 3:09 PM

Comment on lines +20 to +21
/** Whether to use fixed positioning (for fixed navbars) */
useFixedPosition?: boolean;
Copy link
Member

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

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.

2 participants