DropdownMenu Flyout position changes based on mousedown duration about reshaped HOT 3 CLOSED

The button has the correct location on mousedown, just not on mouseup/click, when (I presume) the function that shows the flyout is being called and the location is currently being queried.

Could the correct location not simply be saved upon mousedown in some local state, and then used when the Flyout is being shown?

Otherwise the approach from the video seems decent, at least as a temporary fix, but at the same time this doesn't seem like an "urgent" issue that needs a temporary fix.

from reshaped.

Fixed it, I think the lazy part of me was speaking before since all bounds calculations were happening outside the component 😅
Now I'm saving the bounds on mousedown for cases when user might click the trigger and using the old way as a fallback.

Merging it in a bit, going to be officially announced in 3.2 but will appear in one of the upcoming patch releases as well

from reshaped.

Yes, I can confirm this is happening because of the button scaling.

It seems like the most straightforward way to fix the issue is to temporary drop the transition from the trigger when opening a dropdown. Main tradeoff is that it might not work for all types of transitions (e.g. might be noticeable in case it's used with custom long transition), however it would mean the position is calculated correctly.

Other approach I thought about is to calculate the bounds differently (with offsetTop/Left resolving for example), but that would mean positioning will stop respecting any transforms at all, unless those are calculated manually as well.

An example of the 1st approach, wdyt?

from reshaped.