[Select] Select content position in wrong location
See original GitHub issueBug report
Current Behavior
When a Select is within an element with position: absolute, clicking on the trigger opens the content in a completely different position.
Expected behavior
The content should open right above the trigger.
Reproducible example
Your environment
| Software | Name(s) | Version |
|---|---|---|
| Radix Package(s) | @radix-ui/react-select | 0.1.2-rc.50 |
| React | n/a | |
| Browser | Chrome | |
| Assistive tech | ||
| Node | n/a | |
| npm/yarn | ||
| Operating System |
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Why is the dropdown box of SELECT tag shown at wrong place?
I want it back to the normal place just right below the SELECT element!!! The id of the select tag is just for...
Read more >Dropdown options are displayed in the wrong place. (IE only)
Maning that after I opened dropdown#1 options, and then opened dropdown#2 options - dropdown#2's options will open under dropdown#1 field. See example below....
Read more >Wrap text around a picture in Word - Microsoft Support
Select a picture. · Go to Picture Format or Format > Position, and under Format with Text Wrapping, select Top Left. The Position...
Read more >position - CSS: Cascading Style Sheets - MDN Web Docs
The position CSS property sets how an element is positioned in a document. The top, right, bottom, and left properties determine the final ......
Read more >Understand & manage your location when you search on ...
On your Android device, open the Settings app Settings . · Tap Location and then App permission. · Tap on your browser app,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I’ve determined this was due to other styles being applied via tailwind/daisyui
Ah, I just realised the problem, you are using the latest release candidate, but are not adding the new
Portalpart wrappingContent. If you add it, it should work fine. I’ll close the issue, but let me know if you have other problems.