Open ciampo opened 2 months ago
While https://github.com/WordPress/gutenberg/pull/63357 should avoid the issue for the V2 legacy adapter (soon to be the new V1) component, we will still need to understand how to best solve this for the V2:
flip
disabled (although we could encounter the same issue in future layouts / etc)portal
ed to a plan in the DOM where the stacking context is not a constraints
As flagged in https://github.com/WordPress/gutenberg/pull/62821 (see PR description):
The V2 version of the component automatically "flips" the popover to render on top of the trigger if there isn't enough space below it. In the specific example of the block toolbar, this causes a small visual glitch when the browser's viewport is short enough to cause the flip:
This glitch happens because the block toolbar's header has
position: sticky
, which causes it to render on top of the select popover despite a lowerz-index
.A few preliminary ideas that try to avoid the problem rather than solving it:
I'm not sure we can solve this systematically at the CSS level. At most we could look into where in the DOM the popover is rendered, and consider portalling it so that it plays better with the stacking context?