[Fiber] Run Fragment deletion effects for HostText children - #37168
Conversation
9c03633 to
2d5a72c
Compare
2d5a72c to
c1d3ba3
Compare
c1d3ba3 to
ee3e694
Compare
| if (enableFragmentRefs && enableFragmentRefsTextNodes) { | ||
| commitFragmentInstanceInsertionEffects(finishedWork); | ||
| } | ||
| break; |
There was a problem hiding this comment.
Was it intentional that we no longer run recursivelyTraverseReappearLayoutEffects for HostText? I guess this doesn't change any behavior right now but just want to make sure we're not breaking some implicit assumptions.
There was a problem hiding this comment.
HostText is always a leaf so it should be fine to handle this directly against the node for disappear/reappear
ee3e694 to
4240abd
Compare
4240abd to
25d3ba2
Compare
poteto
left a comment
There was a problem hiding this comment.
LGTM (light skim). Stacking stamps for the fragment-refs land sequence.
HostText entered deletion and disappear/reappear switches past the HostComponent cases that called fragment instance bookkeeping, so text children kept listeners after delete and while Activity-hidden. Handle HostText explicitly in those paths.
25d3ba2 to
1448cff
Compare
|
Comparing: 22e4f99...1448cff Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: (No significant changes) |
) There was inconsistent behavior with text nodes retaining event listeners while all other nodes have them removed in deletion effects. This fixes that handling DiffTrain build for [9880384](react@9880384)
) There was inconsistent behavior with text nodes retaining event listeners while all other nodes have them removed in deletion effects. This fixes that handling DiffTrain build for [9880384](react@9880384)
There was inconsistent behavior with text nodes retaining event listeners while all other nodes have them removed in deletion effects. This fixes that handling