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 077c787
Browse filesBrowse the repository at this point in the historyBrowse files
authored
fix(compilers): textarea value fold must not reserve a hydration id (#3691) (#3696)
* fix(compilers): textarea value fold must not reserve a hydration id (#3691)
The SSR textarea value/defaultValue fold turns the attribute into a
dynamic text child, and that child took the `_$scope` hydration-id
reservation a dynamic hole gets. The client writes the value as a plain
property effect that never allocates an id, so every component after the
textarea hydrated one id off and its updates targeted detached DOM.
Treat the fold like the innerHTML/textContent redirects (#3015): opaque
content, no reservation. Babel flags the folded container with
_childProperty; the native compiler skips the reservation for a
children_replacement. Shared fixture + parity-harness scenario added.
Co-authored-by: Claude via Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
* fix(babel-plugin): use the local @babel/types namespace in the textarea fold flag
The fold's _childProperty cast referenced `babelTypes`, which utils.ts does
not import (it aliases @babel/types as `t`). Rollup's transpile let it
through; the typecheck step did not.
Co-authored-by: Claude via Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
---------
Co-authored-by: Claude via Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
A `<textarea>` with a dynamic `value`/`defaultValue` no longer desyncs hydration ids for the siblings after it (#3691). The server folds the value into the textarea's text content, and that fold was taking the `_$scope` hydration-id reservation a dynamic child hole gets — but the client writes the value as a plain property effect that never allocates an id, so every component after the textarea hydrated one id off and its updates targeted detached DOM. The fold is now treated like the `innerHTML`/`textContent` redirects (#3015): opaque content, no id reservation, in both the Babel plugin and the native compiler.
0 commit comments