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 62e7883
Browse filesBrowse the repository at this point in the historyBrowse files
fix(solid): route pre-flush Loading rejections through the fragment channel (#2997)
An async rejection landing before the shell flushed under Errored > Loading
rendered a permanently blank region: the server called the enclosing
Errored's handler at async time, whose rendered fallback had no consumer,
while the error record it serialized at the boundary id derailed the
hydrating client into claiming fallback DOM that was never emitted. Once a
boundary's fragment is registered, its channel now owns error routing —
`<key>_fr` rejects and the client re-renders the subtree fresh, letting the
client-side Errored catch, exactly like the post-flush path. The sync
discovery pass (pull still on the stack) keeps parent-handler routing and
inline fallbacks. Client-side, the serialized rejected flight and subFetch
trace runs now observe rejections so adoption doesn't leak unhandled
rejection noise.
Co-authored-by: Cursor <[email protected]>
0 commit comments