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
{{ message }}
This repository has been archived by the owner on Dec 5, 2024. It is now read-only.
I am trying to migrate the component to use 2.3.0. However, the documentation is excellent so far. There is no reference on how to keep doing escapeWithReference.
There is information on how it is supposed to behave on https://popper.js.org/docs/v1/#modifierspreventoverflow, but I need clarification on how to persist the original behaviour. Could you give me some guidance on how to do this?
The text was updated successfully, but these errors were encountered:
It's not well documented and is quite confusing because there have been multiple ways to achieve this in past versions, but I think I figured out what is happening in the React Popper (Popper v2.x).
The default flip modifier is causing the popper to try to "flip" positions when it falls out of bounds, trying to keep it in the viewport.
Explicitly adding/overriding the flip modifier with no fallback options is the solution for me that enables the popper to stay attached to its reference element in the position it started in, effectively allowing it to "escape with its reference".
I am trying to migrate the component to use 2.3.0. However, the documentation is excellent so far. There is no reference on how to keep doing
escapeWithReference
.There is information on how it is supposed to behave on https://popper.js.org/docs/v1/#modifierspreventoverflow, but I need clarification on how to persist the original behaviour. Could you give me some guidance on how to do this?
The text was updated successfully, but these errors were encountered: