What happens
When the running overlay menu is used in landscape with live debugging enabled, the debug/result panel can still be laid out as if there is room on the right side of the button cluster. If the overlay is parked near the right edge, that means the debug data opens off-screen and becomes partly or fully clipped.
The same right-side assumption also shows up in smaller UI details: separators and resize transitions were originally authored for a panel that always sits to the right of the buttons.
Why this matters
Landscape use is a natural place to keep the floating toolbar on the left or right edge. In that setup, the toolbar buttons should remain the user-controlled anchor, and the optional debug panel should choose the side that actually fits around that anchor.
Suggested direction
Keep right-side placement as the default, but when the right side cannot fit the full debug/result panel and the left side can fit it with more available room, flip the panel to the left within the same rounded overlay container. Re-run that placement after drag release so the panel does not stay clipped after the user moves the toolbar.
There is one remaining UX caveat: the resize/visibility transition can still use maintainer visual polish. The placement and clipping behavior can be fixed mechanically, but the exact animation should ideally be tuned while watching the overlay on a real device.
What happens
When the running overlay menu is used in landscape with live debugging enabled, the debug/result panel can still be laid out as if there is room on the right side of the button cluster. If the overlay is parked near the right edge, that means the debug data opens off-screen and becomes partly or fully clipped.
The same right-side assumption also shows up in smaller UI details: separators and resize transitions were originally authored for a panel that always sits to the right of the buttons.
Why this matters
Landscape use is a natural place to keep the floating toolbar on the left or right edge. In that setup, the toolbar buttons should remain the user-controlled anchor, and the optional debug panel should choose the side that actually fits around that anchor.
Suggested direction
Keep right-side placement as the default, but when the right side cannot fit the full debug/result panel and the left side can fit it with more available room, flip the panel to the left within the same rounded overlay container. Re-run that placement after drag release so the panel does not stay clipped after the user moves the toolbar.
There is one remaining UX caveat: the resize/visibility transition can still use maintainer visual polish. The placement and clipping behavior can be fixed mechanically, but the exact animation should ideally be tuned while watching the overlay on a real device.