[DevTools] Preserve Suspense lineage when clicking through breadcrumbs #34422
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
React Core Team
eps1lon
force-pushed
the
sebbie/09-08-_devtools_preserve_suspense_lineage_when_clicking_through_suspense_breadcrumbs
branch
from
541d5e8 to
252c8e7
Compare
eps1lon
force-pushed
the
sebbie/09-08-_devtools_preserve_suspense_lineage_when_clicking_through_suspense_breadcrumbs
branch
3 times, most recently
from
57322f4 to
d381773
Compare
eps1lon
force-pushed
the
sebbie/09-08-_devtools_preserve_suspense_lineage_when_clicking_through_suspense_breadcrumbs
branch
from
d381773 to
cde1a32
Compare
sebmarkbage
approved these changes
Sep 10, 2025
eps1lon
deleted the
sebbie/09-08-_devtools_preserve_suspense_lineage_when_clicking_through_suspense_breadcrumbs
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Moves timeline and lineage into state so that we can better reconcile them during Suspense tree changes.
That state could live in TreeStateContext given that we always change inspected Suspense and Element ID together in the Suspense Tab. They're still split for now to avoid re-renders of the Suspense Tab when we're changing Components tab state. Bug mid term they probably end up together. Especially once we implement selecting the nearest Suspense boundary of the inspected Element when navigating to the Suspense tab.
CleanShot.2025-09-09.at.11.11.21.mp4