atomiks

I've re-opened the existing issue that was closed

A cause of this error should be fixed now if you re-install Mantine so it picks up `@floating-ui/[email protected]` (a transitive dependency). Clear the cache and verify if that version successfully...

I deprecated that and pointed to https://floating-ui.com/docs/size as it was buggy in a couple ways — I recommend just switching to Floating UI as it's getting full support and the...

This doesn't actually address the root cause though and will still result in broken positioning. Isn't it this Android issue?

The key issue is the clipping algorithm has a bias toward top/left over bottom/right when both sides are clipped (in this case, the root boundary/viewport and element boundary). - Top...

Not straightforwardly, it would require custom middleware instead of `shift`, and using `detectOverflow` most likely.

@Yegorich555 it doesn't seem like that handles the "root" viewport in the first place. It overflows the viewport if the bottom of the viewport is above the boundary bottom. ---...

I'm talking specifically about multiple boundaries, or in that API, multiple elements for `fitToElement`. If you specify a boundary in Floating UI, it doesn't cause the popover to start overflowing...

It's half-baked and doesn't live up to the necessary standard to be added when compared to the rest of the library. It's also missing the second possibly crucial part which...

Are there cases where you wouldn't want this? Would be better to simply not have an option at all if possible.