useOverlayPosition wrong position when boundary element is set

[RamunasO]

🐛 Bug Report

useOverlayPosition has wrong position when boundary element is set.

🤔 Expected Behavior

It should position overlay correctly.

😯 Current Behavior

Overlay has wrong position.

💁 Possible Solution

Seems like available space and possibly other values are being calculated relative to the body/viewport rather than boundary element. This might only happen if trigger element is within boundary, but not sure.

🔦 Context

In our use case aria overlays need to be fully contained within parent component. Which means portals are attached to that dom node and overlay should be positioned relative to the node.

💻 Code Sample

This is the simplest reproduction I could make based on example in overlay docs.
https://codesandbox.io/s/overlay-position-issue-ysgcsr?file=/src/index.js

[LFDanLu]

I was able to reproduce your issue with the example you provided but got the correct behavior when modifying one of our pre-existing stories locally. Will need to dig into the positioning code to figure out the differences between the two.

EDIT: Did some more tinkering locally, was mistaken about the pre-existing story working positioning is definitely off