fix(react): remove relocated inline overlays orphaned on unmount

[ShaneK]

Issue number: internal

---

What is the current behavior?

Currently, when an inline overlay (ion-modal, ion-popover) is rendered through React and CoreDelegate teleports its host out of the React-rendered location, unmounting the component can leave the host orphaned in the DOM. componentWillUnmount only recovered a relocated host when this.state.isOpen was true, so a host that was moved while still closed was never reattached for React to remove. That happens during the React 18 StrictMode mount/unmount cycle, or any re-render before the present events flip isOpen. The result is duplicate <ion-modal> elements stacking up in document.body. This came from the portal change in #31159

What is the new behavior?

This splits the unmount cleanup into two independent steps. The DOM recovery now runs whenever the host is still connected and has been relocated, regardless of open state: portaled overlays get reattached to portalTarget so React's removeChild can find them, and nested overlays moved out of their <template> are removed directly. The dismiss-lifecycle teardown, detaching the didDismiss listener and props, stays gated on isOpen as before. So a relocated-but-closed host is now cleaned up instead of orphaned.

Does this introduce a breaking change?

• Yes
• No

Other information

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ionic-framework	Ready	Preview, Comment	Jun 16, 2026 7:42pm

[thetaPC]

LGTM