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 0a3793c
Browse filesBrowse the repository at this point in the historyBrowse files
Two mounts under one boundary, made in separate flushes, keep their holds independent (S-5 rows 1′–3′, D-4, #4283). A boundary's tree and output are structure, not a user derivation of its content: like the render effect that flattens the same children without a boundary, they read a hold they are not part of as committed and are re-derived at its landing, and a re-pass of one outside its hold's flush publishes mainline instead of re-joining that hold and merging it with the next flush's. `<Errored>` and `<Loading>` (with or without `on`) around two `<Show>`s, each over its own hold, now reveal each branch at its own hold's landing. A re-arm's swap is still the change's work: while it is, the output joins the change (D-13).
First mounts of a multi-node insert skip `reconcileArrays`' diff setup (spa-navigation mounts ~3%). The once-per-pass focus read from #4261 still applies, so a focused node arriving from another list keeps its focus.
`<Repeat>` with element (non-function) children no longer builds each row twice. It read the `children` getter once to check for a function and again for the value, so every row's JSX ran twice and its refs fired twice (#4296).
Each event replayed after hydration is its own instant, as it would have been live (#4285). `runHydrationEvents` now flushes after every replayed event, so a handler reads the writes of the events before it: two clicks on a counter queued before the client loaded bump it twice, not once.
0 commit comments