You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When two type="push" flyouts share the same padding target (the container prop, or document.body by default), closing both leaves stale inline padding on the target even though no flyout is open. The surrounding page content stays shrunk.
The padding target ends up with a leftover padding-inline-end (or padding-inline-start for side="left"), so any full-width content remains squished with an empty gap where a flyout used to be.
Description
Describe the bug
When two
type="push"flyouts share the same padding target (thecontainerprop, ordocument.bodyby default), closing both leaves stale inline padding on the target even though no flyout is open. The surrounding page content stays shrunk.The padding target ends up with a leftover
padding-inline-end(orpadding-inline-startforside="left"), so any full-width content remains squished with an empty gap where a flyout used to be.Reproduction
CodeSandbox: https://7dy6g2.csb.app
Two independent push flyouts (
pushMinBreakpoint="xs") rendered on the same target (document.body), plus a full-width bar so the shrink is visible.Steps:
After step 4 there is no flyout open, but the page content stays shrunk and the full-width bar keeps a ~384px gap on the right.
Expected behavior
After both flyouts close, the target's
padding-inline-endreturns to its base value ("") and the content goes back to full width.Actual behavior
The target keeps flyout A's applied padding.
Video
Screen.Recording.2026-07-07.at.07.28.41.mov
Related issue on kibana: elastic/kibana#276159