[DevTools] Handle reorders when resuspending while fallback contains Suspense #34225
+284
−73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stacked on #34224
This is reverting #34168 in favor of passing the designated parent to
removePreviousSuspendedBy
.We can't just pop the Suspense nodes after we updated the fallback since the fallback might've inserted a new Suspense node i.e. advanced sibling pointers.
We now no longer pop after reconciling Suspense fallbacks. Callers need to know they don't need to pop when they reconciled Suspense children.