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
{{ message }}
Repository navigation
Commit bc4db2e
Browse filesBrowse the repository at this point in the historyBrowse files
fix(hydration): a hydrated Errored's fallback keeps lazily created content from claiming (#4348)
A hydrated `<Errored>` that shows the server's fallback ran its content in a
claim window over no owner, but the window only covered the content's own
run. Children the content resolves lazily — a context provider's, a function
child, a `children()` accessor, a nested Loading/Errored/Show/For — are
created in the boundary's later flatten, after the window closed, so their
templates tried to claim server DOM the fallback replaced (key misses,
detached elements).
The boundary's owner is now marked when the content runs: `isClaiming` walks
the owner chain and claims nothing under a mark, whenever the node is
created. The served-answer check in readSerializedOrCompute asks about the
window alone, so reruns there keep re-serving. A nested Loading created
where nothing claims takes the unclaimed path and no longer waits on a
fragment the server dropped with the content.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
A hydrated `<Errored>` showing the server's fallback no longer logs `Hydration key miss` (or builds detached elements) for content it creates lazily: children behind a context provider, a component returning a function, a `children()` accessor, or a nested `<Loading>`, `<Errored>`, `<Show>` or `<For>` resolved after the content's own run. Nothing under the boundary claims server DOM, so the fallback stays up until a content input changes or `reset()` (#4348). A nested `<Loading>` there no longer waits on a fragment the server dropped with the content.
0 commit comments