Check For Errors From the Disconnected DOM Node Rehydration Fix

To improve framework consistency, Lightning web components now rehydrate only when they're actively connected to the DOM. For example, rehydration skips detached nodes to prevent lifecycle methods like renderedCallback from firing multiple times. Previously, certain edge cases allowed disconnected DOM nodes to be rehydrated, which could trigger reactive state updates or function invocations on detached components.

Where: This change applies to Lightning Experience, Experience Builder sites, and all versions of the mobile app in all editions. This change also applies to Lightning web components in Open Source.

How: This change is enabled automatically. If your implementation created a dependency on the previous rehydration behavior, review your logic for breakages.