Skip to content

fix(ui): select menu positioning #93684

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

Merged

Conversation

TkDodo
Copy link
Contributor

@TkDodo TkDodo commented Jun 17, 2025

the ...provided spread will give us top/bottom 100% depending on where the menu should be opened, so the hardcoded top:100% is harmful; also, margin top/bottom is provided already

before after
Screenshot 2025-06-17 at 10 15 23 Screenshot 2025-06-17 at 10 15 06

the `...provided` spread will give us top/bottom 100% depending on where the menu should be opened, so the hardcoded top:100% is harmful; also, margin top/bottom is provided already
@TkDodo TkDodo marked this pull request as ready for review June 17, 2025 08:16
@TkDodo TkDodo requested a review from a team as a code owner June 17, 2025 08:16
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 17, 2025
@TkDodo TkDodo merged commit ccd9d91 into master Jun 17, 2025
46 checks passed
@TkDodo TkDodo deleted the tkdodo/fix/de-81-buggy-select-component-dropdown-behavior branch June 17, 2025 13:35
billyvg pushed a commit that referenced this pull request Jun 18, 2025
the `...provided` spread will give us top/bottom 100% depending on where
the menu should be opened, so the hardcoded top:100% is harmful; also,
margin top/bottom is provided already

| before | after |
|--------|--------|
| ![Screenshot 2025-06-17 at 10 15
23](https://github.com/user-attachments/assets/23f5c6d4-4e98-4bb1-a6ec-54a0061e4eb3)
| ![Screenshot 2025-06-17 at 10 15
06](https://github.com/user-attachments/assets/5e96dbb7-459a-4085-b71f-05ab39046a30)
|
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
the `...provided` spread will give us top/bottom 100% depending on where
the menu should be opened, so the hardcoded top:100% is harmful; also,
margin top/bottom is provided already

| before | after |
|--------|--------|
| ![Screenshot 2025-06-17 at 10 15
23](https://github.com/user-attachments/assets/23f5c6d4-4e98-4bb1-a6ec-54a0061e4eb3)
| ![Screenshot 2025-06-17 at 10 15
06](https://github.com/user-attachments/assets/5e96dbb7-459a-4085-b71f-05ab39046a30)
|
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants