You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mainly I would like to request the support for using Popper while using an "absolute" floating strategy rather than fixed.
Eventually, the popper-content-wrapper will get styled with "position: fixed;" and there is no straight-forward way to change it.
Overview
In the codebase you can see that the strategy is hardcoded strategy: 'fixed',
which is the cause of the "position: fixed;" style.
So all components that use the popper must use this "fixed" strategy and it would be quite hard to choose the "absolute" strategy.
The main reason I had this need is due to the following issue:
Popover inside a scrollable container will appear outside of the container when exceeding its boundaries, even if its anchor is in the hidden overflown section of the container:
In order to solve that issue I had to add {absolute: !important} to css because the data-radix-popper-content-wrapper's fixed position is set as a style:
Feature request
Mainly I would like to request the support for using Popper while using an "absolute" floating strategy rather than fixed.
Eventually, the popper-content-wrapper will get styled with "position: fixed;" and there is no straight-forward way to change it.
Overview
In the codebase you can see that the strategy is hardcoded
strategy: 'fixed',
which is the cause of the "position: fixed;" style.
So all components that use the popper must use this "fixed" strategy and it would be quite hard to choose the "absolute" strategy.
The main reason I had this need is due to the following issue:
Popover inside a scrollable container will appear outside of the container when exceeding its boundaries, even if its anchor is in the hidden overflown section of the container:
Issue Example on Codesandbox
![Screenshot 2024-05-18 at 14 27 34](https://private-user-images.githubusercontent.com/10271715/331796066-3de21708-2fdb-4a2b-b90c-34e81cc3d1ca.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk2MjQ0MzAsIm5iZiI6MTcxOTYyNDEzMCwicGF0aCI6Ii8xMDI3MTcxNS8zMzE3OTYwNjYtM2RlMjE3MDgtMmZkYi00YTJiLWI5MGMtMzRlODFjYzNkMWNhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjI5VDAxMjIxMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNhYzdkYTBjMDU5ODJjOGQwYzkzYjAwY2ZiNmM3NWQ5MjY2MmQzODE1Nzk3OGFkMjE2ODhlMmI1ZDc2NzUwMWUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Sxmvy7YfoAW50qgPdPyR0PpDcb1hZMSdji555YW6cWk)
Who does this impact? Who is this for?
I think it might impact everyone
Additional context
In order to solve that issue I had to add {absolute: !important} to css because the data-radix-popper-content-wrapper's fixed position is set as a style:
Hack Solution Example in Codesandbox
![Screenshot 2024-05-18 at 14 24 12](https://private-user-images.githubusercontent.com/10271715/331795872-20847dfa-9f76-46e4-889d-b3a5ec75186c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk2MjQ0MzAsIm5iZiI6MTcxOTYyNDEzMCwicGF0aCI6Ii8xMDI3MTcxNS8zMzE3OTU4NzItMjA4NDdkZmEtOWY3Ni00NmU0LTg4OWQtYjNhNWVjNzUxODZjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjI5VDAxMjIxMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc3ZTg5ODE3NTU3MjhhYWM5ZTZhMmZjZmExOGIwOTc4ZjEwMzg5MmNmZGI5NjNlODU4NGIwZDk2NWJjNjZhMTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Ps0tmjLeytX-iSJtsLrfzQo8yu6Uh6vl3deSes_mOOI)
The text was updated successfully, but these errors were encountered: