[DevTools] Fix WhatChanged scrolling out of view in profiler sidebar by Kertsu · Pull Request #36244 · react/react

Kertsu · 2026-04-09T16:12:19Z

Summary

Previously, WhatChanged and InspectedElementBadges were rendered inside the same scrollable Content div as the commit list. When a component had many render timestamps, scrolling down to pick one caused the "what changed" context to scroll out of view, requiring the user to scroll back up to see it.

While the profiler already exposes render details via hover tooltips on fibers, those are transient and pointer-dependent. This change introduces a sticky header section at the top of the Content div that holds the current commit summary, badges, and WhatChanged. The section is collapsible (click or Enter/Space) so users can reclaim vertical space for the commit list when needed. The commit list now sits below the sticky header as a sibling, so it scrolls independently while the summary remains always visible.

Closes#36525

Current Behavior

current-behavior.mov

Proposed UI

Apologies on this one. I had to upload it on YouTube since the video is quite big.

How did you test this change?

Manual Testing

Case	Screenshot
Expanded simple
Collapsed Simple
Focused using tab navigation while expanded
Focused using tab navigation while collapsed
Long render info( expanded )
Long render info( collapsed )

Hover (expanded)

expanded-hover-simple.mov

Hover (collapsed)

collapsed-hover-simple.mov

Why this matters

This is more than a visual polish issue:

The Profiler is fundamentally a context-driven debugging tool
Losing the “why did this render?” explanation during navigation interrupts analysis flow
The issue becomes progressively worse on large applications or heavily interactive surfaces
Hover tooltips are not an adequate replacement because they are transient and pointer-dependent
Keyboard users are disproportionately affected due to repeated navigation and scrolling

In practice, this increases cognitive load during performance debugging and makes long profiling sessions unnecessarily cumbersome.

Kertsu · 2026-04-25T08:00:47Z

Bumping this in case it got buried, @eps1lon @hoxyq. Happy to address any feedback or adjust the approach if the sticky header pattern isn't the direction you'd want 🙌🏻

hoxyq

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?

Without any expand / collapse mechanics, I think that should address the issue?

hoxyq · 2026-06-23T12:29:17Z

+ // $FlowFixMe[missing-local-annot]
+ const handleKeyDown = event => {
+ if (event.key === 'Enter' || event.key === ' ') {
+ // Prevent the browser from scrolling down when Space is pressed
+ if (event.key === ' ') {
+ event.preventDefault();
+ }
+ toggleCollapsedVal();
+ }
+ };


Please add annotation to this callback

Applied in ff7fb87

hoxyq · 2026-06-23T12:31:17Z

Also, please see failed Flow jobs, you can reproduce it locally with yarn flow dom-browser.

Kertsu · 2026-06-26T01:13:39Z

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?
Without any expand / collapse mechanics, I think that should address the issue?

Thanks for the feedback, @hoxyq!

Yes, that was my original instinct too. Just lift WhatChanged and the badges out of the scroll container so they sit above the commit list as a static subheader.

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That said, I understand this adds interaction complexity that may not be in line with the existing DevTools patterns. Happy to drop it and go with the simpler non-collapsible sticky subheader if you think the tradeoff is acceptable.

Just want to make sure we're aligned before I push another revision.

hoxyq

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

hoxyq · 2026-07-06T14:08:00Z

Could you please attach a screenshot / screencast of the new behaviour?

Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Kertsu · 2026-07-06T15:38:02Z

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

Ooh okay, I see. Thanks for this. Will be making some changes!

Kertsu · 2026-07-06T15:38:30Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Yup, sure. Thanks for the reference.

Kertsu · 2026-07-06T18:09:49Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

For the badges and what changed, I just used dummy data for manual testing. This is how it looks like. Let me know what you think, @hoxyq 🙌🏻

with.commit.list.container.mov

Previously, WhatChanged and InspectedElementBadges were rendered in the same scrollable container as the commit list. When a component had many render timestamps, scrolling through the commit history also scrolled the render summary out of view, requiring users to repeatedly scroll back to regain context. This change separates the render summary from the commit history by making only the commit list scrollable. WhatChanged and InspectedElementBadges remain fixed at the top of the sidebar while the render timestamps scroll independently, keeping the currently selected commit's context visible throughout navigation without additional interaction. Closesreact#36525 References: - https://github.com/facebook/react/blob/main/packages/react-devtools-shared/src/devtools/views/Profiler/SidebarSelectedFiberInfo.js#L132-L149

hoxyq

Thanks!

hoxyq

Thanks!

Kertsu · 2026-07-07T13:23:36Z

Thanks, @hoxyq! This is my first-ever meaningful contribution to an open source project as iconic as React 🚀

Kertsu · 2026-04-09T16:12:19Z

Summary

Previously, WhatChanged and InspectedElementBadges were rendered inside the same scrollable Content div as the commit list. When a component had many render timestamps, scrolling down to pick one caused the "what changed" context to scroll out of view, requiring the user to scroll back up to see it.

While the profiler already exposes render details via hover tooltips on fibers, those are transient and pointer-dependent. This change introduces a sticky header section at the top of the Content div that holds the current commit summary, badges, and WhatChanged. The section is collapsible (click or Enter/Space) so users can reclaim vertical space for the commit list when needed. The commit list now sits below the sticky header as a sibling, so it scrolls independently while the summary remains always visible.

Closes#36525

Current Behavior

current-behavior.mov

Proposed UI

Apologies on this one. I had to upload it on YouTube since the video is quite big.

How did you test this change?

Manual Testing

Case	Screenshot
Expanded simple
Collapsed Simple
Focused using tab navigation while expanded
Focused using tab navigation while collapsed
Long render info( expanded )
Long render info( collapsed )

Hover (expanded)

expanded-hover-simple.mov

Hover (collapsed)

collapsed-hover-simple.mov

Why this matters

This is more than a visual polish issue:

The Profiler is fundamentally a context-driven debugging tool
Losing the “why did this render?” explanation during navigation interrupts analysis flow
The issue becomes progressively worse on large applications or heavily interactive surfaces
Hover tooltips are not an adequate replacement because they are transient and pointer-dependent
Keyboard users are disproportionately affected due to repeated navigation and scrolling

In practice, this increases cognitive load during performance debugging and makes long profiling sessions unnecessarily cumbersome.

Kertsu · 2026-04-25T08:00:47Z

Bumping this in case it got buried, @eps1lon @hoxyq. Happy to address any feedback or adjust the approach if the sticky header pattern isn't the direction you'd want 🙌🏻

hoxyq

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?

Without any expand / collapse mechanics, I think that should address the issue?

hoxyq · 2026-06-23T12:29:17Z

+ // $FlowFixMe[missing-local-annot]
+ const handleKeyDown = event => {
+ if (event.key === 'Enter' || event.key === ' ') {
+ // Prevent the browser from scrolling down when Space is pressed
+ if (event.key === ' ') {
+ event.preventDefault();
+ }
+ toggleCollapsedVal();
+ }
+ };


Please add annotation to this callback

Applied in ff7fb87

hoxyq · 2026-06-23T12:31:17Z

Also, please see failed Flow jobs, you can reproduce it locally with yarn flow dom-browser.

Kertsu · 2026-06-26T01:13:39Z

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?
Without any expand / collapse mechanics, I think that should address the issue?

Thanks for the feedback, @hoxyq!

Yes, that was my original instinct too. Just lift WhatChanged and the badges out of the scroll container so they sit above the commit list as a static subheader.

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That said, I understand this adds interaction complexity that may not be in line with the existing DevTools patterns. Happy to drop it and go with the simpler non-collapsible sticky subheader if you think the tradeoff is acceptable.

Just want to make sure we're aligned before I push another revision.

hoxyq

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

hoxyq · 2026-07-06T14:08:00Z

Could you please attach a screenshot / screencast of the new behaviour?

Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Kertsu · 2026-07-06T15:38:02Z

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

Ooh okay, I see. Thanks for this. Will be making some changes!

Kertsu · 2026-07-06T15:38:30Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Yup, sure. Thanks for the reference.

Kertsu · 2026-07-06T18:09:49Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

For the badges and what changed, I just used dummy data for manual testing. This is how it looks like. Let me know what you think, @hoxyq 🙌🏻

with.commit.list.container.mov

Previously, WhatChanged and InspectedElementBadges were rendered in the same scrollable container as the commit list. When a component had many render timestamps, scrolling through the commit history also scrolled the render summary out of view, requiring users to repeatedly scroll back to regain context. This change separates the render summary from the commit history by making only the commit list scrollable. WhatChanged and InspectedElementBadges remain fixed at the top of the sidebar while the render timestamps scroll independently, keeping the currently selected commit's context visible throughout navigation without additional interaction. Closesreact#36525 References: - https://github.com/facebook/react/blob/main/packages/react-devtools-shared/src/devtools/views/Profiler/SidebarSelectedFiberInfo.js#L132-L149

hoxyq

Thanks!

hoxyq

Thanks!

Kertsu · 2026-07-07T13:23:36Z

Thanks, @hoxyq! This is my first-ever meaningful contribution to an open source project as iconic as React 🚀

Kertsu · 2026-04-09T16:12:19Z

Summary

Previously, WhatChanged and InspectedElementBadges were rendered inside the same scrollable Content div as the commit list. When a component had many render timestamps, scrolling down to pick one caused the "what changed" context to scroll out of view, requiring the user to scroll back up to see it.

While the profiler already exposes render details via hover tooltips on fibers, those are transient and pointer-dependent. This change introduces a sticky header section at the top of the Content div that holds the current commit summary, badges, and WhatChanged. The section is collapsible (click or Enter/Space) so users can reclaim vertical space for the commit list when needed. The commit list now sits below the sticky header as a sibling, so it scrolls independently while the summary remains always visible.

Closes#36525

Current Behavior

current-behavior.mov

Proposed UI

Apologies on this one. I had to upload it on YouTube since the video is quite big.

How did you test this change?

Manual Testing

Case	Screenshot
Expanded simple
Collapsed Simple
Focused using tab navigation while expanded
Focused using tab navigation while collapsed
Long render info( expanded )
Long render info( collapsed )

Hover (expanded)

expanded-hover-simple.mov

Hover (collapsed)

collapsed-hover-simple.mov

Why this matters

This is more than a visual polish issue:

The Profiler is fundamentally a context-driven debugging tool
Losing the “why did this render?” explanation during navigation interrupts analysis flow
The issue becomes progressively worse on large applications or heavily interactive surfaces
Hover tooltips are not an adequate replacement because they are transient and pointer-dependent
Keyboard users are disproportionately affected due to repeated navigation and scrolling

In practice, this increases cognitive load during performance debugging and makes long profiling sessions unnecessarily cumbersome.

Kertsu · 2026-04-25T08:00:47Z

Bumping this in case it got buried, @eps1lon @hoxyq. Happy to address any feedback or adjust the approach if the sticky header pattern isn't the direction you'd want 🙌🏻

hoxyq

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?

Without any expand / collapse mechanics, I think that should address the issue?

hoxyq · 2026-06-23T12:29:17Z

+ // $FlowFixMe[missing-local-annot]
+ const handleKeyDown = event => {
+ if (event.key === 'Enter' || event.key === ' ') {
+ // Prevent the browser from scrolling down when Space is pressed
+ if (event.key === ' ') {
+ event.preventDefault();
+ }
+ toggleCollapsedVal();
+ }
+ };


Please add annotation to this callback

Applied in ff7fb87

hoxyq · 2026-06-23T12:31:17Z

Also, please see failed Flow jobs, you can reproduce it locally with yarn flow dom-browser.

Kertsu · 2026-06-26T01:13:39Z

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?
Without any expand / collapse mechanics, I think that should address the issue?

Thanks for the feedback, @hoxyq!

Yes, that was my original instinct too. Just lift WhatChanged and the badges out of the scroll container so they sit above the commit list as a static subheader.

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That said, I understand this adds interaction complexity that may not be in line with the existing DevTools patterns. Happy to drop it and go with the simpler non-collapsible sticky subheader if you think the tradeoff is acceptable.

Just want to make sure we're aligned before I push another revision.

hoxyq

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

hoxyq · 2026-07-06T14:08:00Z

Could you please attach a screenshot / screencast of the new behaviour?

Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Kertsu · 2026-07-06T15:38:02Z

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

Ooh okay, I see. Thanks for this. Will be making some changes!

Kertsu · 2026-07-06T15:38:30Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Yup, sure. Thanks for the reference.

Kertsu · 2026-07-06T18:09:49Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

For the badges and what changed, I just used dummy data for manual testing. This is how it looks like. Let me know what you think, @hoxyq 🙌🏻

with.commit.list.container.mov

Previously, WhatChanged and InspectedElementBadges were rendered in the same scrollable container as the commit list. When a component had many render timestamps, scrolling through the commit history also scrolled the render summary out of view, requiring users to repeatedly scroll back to regain context. This change separates the render summary from the commit history by making only the commit list scrollable. WhatChanged and InspectedElementBadges remain fixed at the top of the sidebar while the render timestamps scroll independently, keeping the currently selected commit's context visible throughout navigation without additional interaction. Closesreact#36525 References: - https://github.com/facebook/react/blob/main/packages/react-devtools-shared/src/devtools/views/Profiler/SidebarSelectedFiberInfo.js#L132-L149

hoxyq

Thanks!

hoxyq

Thanks!

Kertsu · 2026-07-07T13:23:36Z

Thanks, @hoxyq! This is my first-ever meaningful contribution to an open source project as iconic as React 🚀

Kertsu · 2026-04-09T16:12:19Z

Summary

Previously, WhatChanged and InspectedElementBadges were rendered inside the same scrollable Content div as the commit list. When a component had many render timestamps, scrolling down to pick one caused the "what changed" context to scroll out of view, requiring the user to scroll back up to see it.

While the profiler already exposes render details via hover tooltips on fibers, those are transient and pointer-dependent. This change introduces a sticky header section at the top of the Content div that holds the current commit summary, badges, and WhatChanged. The section is collapsible (click or Enter/Space) so users can reclaim vertical space for the commit list when needed. The commit list now sits below the sticky header as a sibling, so it scrolls independently while the summary remains always visible.

Closes#36525

Current Behavior

current-behavior.mov

Proposed UI

Apologies on this one. I had to upload it on YouTube since the video is quite big.

How did you test this change?

Manual Testing

Case	Screenshot
Expanded simple
Collapsed Simple
Focused using tab navigation while expanded
Focused using tab navigation while collapsed
Long render info( expanded )
Long render info( collapsed )

Hover (expanded)

expanded-hover-simple.mov

Hover (collapsed)

collapsed-hover-simple.mov

Why this matters

This is more than a visual polish issue:

The Profiler is fundamentally a context-driven debugging tool
Losing the “why did this render?” explanation during navigation interrupts analysis flow
The issue becomes progressively worse on large applications or heavily interactive surfaces
Hover tooltips are not an adequate replacement because they are transient and pointer-dependent
Keyboard users are disproportionately affected due to repeated navigation and scrolling

In practice, this increases cognitive load during performance debugging and makes long profiling sessions unnecessarily cumbersome.

Kertsu · 2026-04-25T08:00:47Z

Bumping this in case it got buried, @eps1lon @hoxyq. Happy to address any feedback or adjust the approach if the sticky header pattern isn't the direction you'd want 🙌🏻

hoxyq

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?

Without any expand / collapse mechanics, I think that should address the issue?

hoxyq · 2026-06-23T12:29:17Z

+ // $FlowFixMe[missing-local-annot]
+ const handleKeyDown = event => {
+ if (event.key === 'Enter' || event.key === ' ') {
+ // Prevent the browser from scrolling down when Space is pressed
+ if (event.key === ' ') {
+ event.preventDefault();
+ }
+ toggleCollapsedVal();
+ }
+ };


Please add annotation to this callback

Applied in ff7fb87

hoxyq · 2026-06-23T12:31:17Z

Also, please see failed Flow jobs, you can reproduce it locally with yarn flow dom-browser.

Kertsu · 2026-06-26T01:13:39Z

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?
Without any expand / collapse mechanics, I think that should address the issue?

Thanks for the feedback, @hoxyq!

Yes, that was my original instinct too. Just lift WhatChanged and the badges out of the scroll container so they sit above the commit list as a static subheader.

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That said, I understand this adds interaction complexity that may not be in line with the existing DevTools patterns. Happy to drop it and go with the simpler non-collapsible sticky subheader if you think the tradeoff is acceptable.

Just want to make sure we're aligned before I push another revision.

hoxyq

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

hoxyq · 2026-07-06T14:08:00Z

Could you please attach a screenshot / screencast of the new behaviour?

Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Kertsu · 2026-07-06T15:38:02Z

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

Ooh okay, I see. Thanks for this. Will be making some changes!

Kertsu · 2026-07-06T15:38:30Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Yup, sure. Thanks for the reference.

Kertsu · 2026-07-06T18:09:49Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

For the badges and what changed, I just used dummy data for manual testing. This is how it looks like. Let me know what you think, @hoxyq 🙌🏻

with.commit.list.container.mov

Previously, WhatChanged and InspectedElementBadges were rendered in the same scrollable container as the commit list. When a component had many render timestamps, scrolling through the commit history also scrolled the render summary out of view, requiring users to repeatedly scroll back to regain context. This change separates the render summary from the commit history by making only the commit list scrollable. WhatChanged and InspectedElementBadges remain fixed at the top of the sidebar while the render timestamps scroll independently, keeping the currently selected commit's context visible throughout navigation without additional interaction. Closesreact#36525 References: - https://github.com/facebook/react/blob/main/packages/react-devtools-shared/src/devtools/views/Profiler/SidebarSelectedFiberInfo.js#L132-L149

hoxyq

Thanks!

hoxyq

Thanks!

Kertsu · 2026-07-07T13:23:36Z

Thanks, @hoxyq! This is my first-ever meaningful contribution to an open source project as iconic as React 🚀

Kertsu · 2026-04-09T16:12:19Z

Summary

Previously, WhatChanged and InspectedElementBadges were rendered inside the same scrollable Content div as the commit list. When a component had many render timestamps, scrolling down to pick one caused the "what changed" context to scroll out of view, requiring the user to scroll back up to see it.

While the profiler already exposes render details via hover tooltips on fibers, those are transient and pointer-dependent. This change introduces a sticky header section at the top of the Content div that holds the current commit summary, badges, and WhatChanged. The section is collapsible (click or Enter/Space) so users can reclaim vertical space for the commit list when needed. The commit list now sits below the sticky header as a sibling, so it scrolls independently while the summary remains always visible.

Closes#36525

Current Behavior

current-behavior.mov

Proposed UI

Apologies on this one. I had to upload it on YouTube since the video is quite big.

How did you test this change?

Manual Testing

Case	Screenshot
Expanded simple
Collapsed Simple
Focused using tab navigation while expanded
Focused using tab navigation while collapsed
Long render info( expanded )
Long render info( collapsed )

Hover (expanded)

expanded-hover-simple.mov

Hover (collapsed)

collapsed-hover-simple.mov

Why this matters

This is more than a visual polish issue:

The Profiler is fundamentally a context-driven debugging tool
Losing the “why did this render?” explanation during navigation interrupts analysis flow
The issue becomes progressively worse on large applications or heavily interactive surfaces
Hover tooltips are not an adequate replacement because they are transient and pointer-dependent
Keyboard users are disproportionately affected due to repeated navigation and scrolling

In practice, this increases cognitive load during performance debugging and makes long profiling sessions unnecessarily cumbersome.

Kertsu · 2026-04-25T08:00:47Z

Bumping this in case it got buried, @eps1lon @hoxyq. Happy to address any feedback or adjust the approach if the sticky header pattern isn't the direction you'd want 🙌🏻

hoxyq

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?

Without any expand / collapse mechanics, I think that should address the issue?

hoxyq · 2026-06-23T12:29:17Z

+ // $FlowFixMe[missing-local-annot]
+ const handleKeyDown = event => {
+ if (event.key === 'Enter' || event.key === ' ') {
+ // Prevent the browser from scrolling down when Space is pressed
+ if (event.key === ' ') {
+ event.preventDefault();
+ }
+ toggleCollapsedVal();
+ }
+ };


Please add annotation to this callback

Applied in ff7fb87

hoxyq · 2026-06-23T12:31:17Z

Also, please see failed Flow jobs, you can reproduce it locally with yarn flow dom-browser.

Kertsu · 2026-06-26T01:13:39Z

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?
Without any expand / collapse mechanics, I think that should address the issue?

Thanks for the feedback, @hoxyq!

Yes, that was my original instinct too. Just lift WhatChanged and the badges out of the scroll container so they sit above the commit list as a static subheader.

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That said, I understand this adds interaction complexity that may not be in line with the existing DevTools patterns. Happy to drop it and go with the simpler non-collapsible sticky subheader if you think the tradeoff is acceptable.

Just want to make sure we're aligned before I push another revision.

hoxyq

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

hoxyq · 2026-07-06T14:08:00Z

Could you please attach a screenshot / screencast of the new behaviour?

Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Kertsu · 2026-07-06T15:38:02Z

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

Ooh okay, I see. Thanks for this. Will be making some changes!

Kertsu · 2026-07-06T15:38:30Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Yup, sure. Thanks for the reference.

Kertsu · 2026-07-06T18:09:49Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

For the badges and what changed, I just used dummy data for manual testing. This is how it looks like. Let me know what you think, @hoxyq 🙌🏻

with.commit.list.container.mov

Previously, WhatChanged and InspectedElementBadges were rendered in the same scrollable container as the commit list. When a component had many render timestamps, scrolling through the commit history also scrolled the render summary out of view, requiring users to repeatedly scroll back to regain context. This change separates the render summary from the commit history by making only the commit list scrollable. WhatChanged and InspectedElementBadges remain fixed at the top of the sidebar while the render timestamps scroll independently, keeping the currently selected commit's context visible throughout navigation without additional interaction. Closesreact#36525 References: - https://github.com/facebook/react/blob/main/packages/react-devtools-shared/src/devtools/views/Profiler/SidebarSelectedFiberInfo.js#L132-L149

hoxyq

Thanks!

hoxyq

Thanks!

Kertsu · 2026-07-07T13:23:36Z

Thanks, @hoxyq! This is my first-ever meaningful contribution to an open source project as iconic as React 🚀

Kertsu · 2026-04-09T16:12:19Z

Summary

Previously, WhatChanged and InspectedElementBadges were rendered inside the same scrollable Content div as the commit list. When a component had many render timestamps, scrolling down to pick one caused the "what changed" context to scroll out of view, requiring the user to scroll back up to see it.

While the profiler already exposes render details via hover tooltips on fibers, those are transient and pointer-dependent. This change introduces a sticky header section at the top of the Content div that holds the current commit summary, badges, and WhatChanged. The section is collapsible (click or Enter/Space) so users can reclaim vertical space for the commit list when needed. The commit list now sits below the sticky header as a sibling, so it scrolls independently while the summary remains always visible.

Closes#36525

Current Behavior

current-behavior.mov

Proposed UI

Apologies on this one. I had to upload it on YouTube since the video is quite big.

How did you test this change?

Manual Testing

Case	Screenshot
Expanded simple
Collapsed Simple
Focused using tab navigation while expanded
Focused using tab navigation while collapsed
Long render info( expanded )
Long render info( collapsed )

Hover (expanded)

expanded-hover-simple.mov

Hover (collapsed)

collapsed-hover-simple.mov

Why this matters

This is more than a visual polish issue:

The Profiler is fundamentally a context-driven debugging tool
Losing the “why did this render?” explanation during navigation interrupts analysis flow
The issue becomes progressively worse on large applications or heavily interactive surfaces
Hover tooltips are not an adequate replacement because they are transient and pointer-dependent
Keyboard users are disproportionately affected due to repeated navigation and scrolling

In practice, this increases cognitive load during performance debugging and makes long profiling sessions unnecessarily cumbersome.

Kertsu · 2026-04-25T08:00:47Z

Bumping this in case it got buried, @eps1lon @hoxyq. Happy to address any feedback or adjust the approach if the sticky header pattern isn't the direction you'd want 🙌🏻

hoxyq

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?

Without any expand / collapse mechanics, I think that should address the issue?

hoxyq · 2026-06-23T12:29:17Z

+ // $FlowFixMe[missing-local-annot]
+ const handleKeyDown = event => {
+ if (event.key === 'Enter' || event.key === ' ') {
+ // Prevent the browser from scrolling down when Space is pressed
+ if (event.key === ' ') {
+ event.preventDefault();
+ }
+ toggleCollapsedVal();
+ }
+ };


Please add annotation to this callback

Applied in ff7fb87

hoxyq · 2026-06-23T12:31:17Z

Also, please see failed Flow jobs, you can reproduce it locally with yarn flow dom-browser.

Kertsu · 2026-06-26T01:13:39Z

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?
Without any expand / collapse mechanics, I think that should address the issue?

Thanks for the feedback, @hoxyq!

Yes, that was my original instinct too. Just lift WhatChanged and the badges out of the scroll container so they sit above the commit list as a static subheader.

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That said, I understand this adds interaction complexity that may not be in line with the existing DevTools patterns. Happy to drop it and go with the simpler non-collapsible sticky subheader if you think the tradeoff is acceptable.

Just want to make sure we're aligned before I push another revision.

hoxyq

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

hoxyq · 2026-07-06T14:08:00Z

Could you please attach a screenshot / screencast of the new behaviour?

Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Kertsu · 2026-07-06T15:38:02Z

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

Ooh okay, I see. Thanks for this. Will be making some changes!

Kertsu · 2026-07-06T15:38:30Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Yup, sure. Thanks for the reference.

Kertsu · 2026-07-06T18:09:49Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

For the badges and what changed, I just used dummy data for manual testing. This is how it looks like. Let me know what you think, @hoxyq 🙌🏻

with.commit.list.container.mov

Previously, WhatChanged and InspectedElementBadges were rendered in the same scrollable container as the commit list. When a component had many render timestamps, scrolling through the commit history also scrolled the render summary out of view, requiring users to repeatedly scroll back to regain context. This change separates the render summary from the commit history by making only the commit list scrollable. WhatChanged and InspectedElementBadges remain fixed at the top of the sidebar while the render timestamps scroll independently, keeping the currently selected commit's context visible throughout navigation without additional interaction. Closesreact#36525 References: - https://github.com/facebook/react/blob/main/packages/react-devtools-shared/src/devtools/views/Profiler/SidebarSelectedFiberInfo.js#L132-L149

hoxyq

Thanks!

hoxyq

Thanks!

Kertsu · 2026-07-07T13:23:36Z

Thanks, @hoxyq! This is my first-ever meaningful contribution to an open source project as iconic as React 🚀

Kertsu · 2026-04-09T16:12:19Z

Summary

Previously, WhatChanged and InspectedElementBadges were rendered inside the same scrollable Content div as the commit list. When a component had many render timestamps, scrolling down to pick one caused the "what changed" context to scroll out of view, requiring the user to scroll back up to see it.

While the profiler already exposes render details via hover tooltips on fibers, those are transient and pointer-dependent. This change introduces a sticky header section at the top of the Content div that holds the current commit summary, badges, and WhatChanged. The section is collapsible (click or Enter/Space) so users can reclaim vertical space for the commit list when needed. The commit list now sits below the sticky header as a sibling, so it scrolls independently while the summary remains always visible.

Closes#36525

Current Behavior

current-behavior.mov

Proposed UI

Apologies on this one. I had to upload it on YouTube since the video is quite big.

How did you test this change?

Manual Testing

Case	Screenshot
Expanded simple
Collapsed Simple
Focused using tab navigation while expanded
Focused using tab navigation while collapsed
Long render info( expanded )
Long render info( collapsed )

Hover (expanded)

expanded-hover-simple.mov

Hover (collapsed)

collapsed-hover-simple.mov

Why this matters

This is more than a visual polish issue:

The Profiler is fundamentally a context-driven debugging tool
Losing the “why did this render?” explanation during navigation interrupts analysis flow
The issue becomes progressively worse on large applications or heavily interactive surfaces
Hover tooltips are not an adequate replacement because they are transient and pointer-dependent
Keyboard users are disproportionately affected due to repeated navigation and scrolling

In practice, this increases cognitive load during performance debugging and makes long profiling sessions unnecessarily cumbersome.

Kertsu · 2026-04-25T08:00:47Z

Bumping this in case it got buried, @eps1lon @hoxyq. Happy to address any feedback or adjust the approach if the sticky header pattern isn't the direction you'd want 🙌🏻

hoxyq

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?

Without any expand / collapse mechanics, I think that should address the issue?

hoxyq · 2026-06-23T12:29:17Z

+ // $FlowFixMe[missing-local-annot]
+ const handleKeyDown = event => {
+ if (event.key === 'Enter' || event.key === ' ') {
+ // Prevent the browser from scrolling down when Space is pressed
+ if (event.key === ' ') {
+ event.preventDefault();
+ }
+ toggleCollapsedVal();
+ }
+ };


Please add annotation to this callback

Applied in ff7fb87

hoxyq · 2026-06-23T12:31:17Z

Also, please see failed Flow jobs, you can reproduce it locally with yarn flow dom-browser.

Kertsu · 2026-06-26T01:13:39Z

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?
Without any expand / collapse mechanics, I think that should address the issue?

Thanks for the feedback, @hoxyq!

Yes, that was my original instinct too. Just lift WhatChanged and the badges out of the scroll container so they sit above the commit list as a static subheader.

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That said, I understand this adds interaction complexity that may not be in line with the existing DevTools patterns. Happy to drop it and go with the simpler non-collapsible sticky subheader if you think the tradeoff is acceptable.

Just want to make sure we're aligned before I push another revision.

hoxyq

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

hoxyq · 2026-07-06T14:08:00Z

Could you please attach a screenshot / screencast of the new behaviour?

Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Kertsu · 2026-07-06T15:38:02Z

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

Ooh okay, I see. Thanks for this. Will be making some changes!

Kertsu · 2026-07-06T15:38:30Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Yup, sure. Thanks for the reference.

Kertsu · 2026-07-06T18:09:49Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

For the badges and what changed, I just used dummy data for manual testing. This is how it looks like. Let me know what you think, @hoxyq 🙌🏻

with.commit.list.container.mov

Previously, WhatChanged and InspectedElementBadges were rendered in the same scrollable container as the commit list. When a component had many render timestamps, scrolling through the commit history also scrolled the render summary out of view, requiring users to repeatedly scroll back to regain context. This change separates the render summary from the commit history by making only the commit list scrollable. WhatChanged and InspectedElementBadges remain fixed at the top of the sidebar while the render timestamps scroll independently, keeping the currently selected commit's context visible throughout navigation without additional interaction. Closesreact#36525 References: - https://github.com/facebook/react/blob/main/packages/react-devtools-shared/src/devtools/views/Profiler/SidebarSelectedFiberInfo.js#L132-L149

hoxyq

Thanks!

hoxyq

Thanks!

Kertsu · 2026-07-07T13:23:36Z

Thanks, @hoxyq! This is my first-ever meaningful contribution to an open source project as iconic as React 🚀

Kertsu · 2026-04-09T16:12:19Z

Summary

Previously, WhatChanged and InspectedElementBadges were rendered inside the same scrollable Content div as the commit list. When a component had many render timestamps, scrolling down to pick one caused the "what changed" context to scroll out of view, requiring the user to scroll back up to see it.

While the profiler already exposes render details via hover tooltips on fibers, those are transient and pointer-dependent. This change introduces a sticky header section at the top of the Content div that holds the current commit summary, badges, and WhatChanged. The section is collapsible (click or Enter/Space) so users can reclaim vertical space for the commit list when needed. The commit list now sits below the sticky header as a sibling, so it scrolls independently while the summary remains always visible.

Closes#36525

Current Behavior

current-behavior.mov

Proposed UI

Apologies on this one. I had to upload it on YouTube since the video is quite big.

How did you test this change?

Manual Testing

Case	Screenshot
Expanded simple
Collapsed Simple
Focused using tab navigation while expanded
Focused using tab navigation while collapsed
Long render info( expanded )
Long render info( collapsed )

Hover (expanded)

expanded-hover-simple.mov

Hover (collapsed)

collapsed-hover-simple.mov

Why this matters

This is more than a visual polish issue:

The Profiler is fundamentally a context-driven debugging tool
Losing the “why did this render?” explanation during navigation interrupts analysis flow
The issue becomes progressively worse on large applications or heavily interactive surfaces
Hover tooltips are not an adequate replacement because they are transient and pointer-dependent
Keyboard users are disproportionately affected due to repeated navigation and scrolling

In practice, this increases cognitive load during performance debugging and makes long profiling sessions unnecessarily cumbersome.

Kertsu · 2026-04-25T08:00:47Z

Bumping this in case it got buried, @eps1lon @hoxyq. Happy to address any feedback or adjust the approach if the sticky header pattern isn't the direction you'd want 🙌🏻

hoxyq

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?

Without any expand / collapse mechanics, I think that should address the issue?

hoxyq · 2026-06-23T12:29:17Z

+ // $FlowFixMe[missing-local-annot]
+ const handleKeyDown = event => {
+ if (event.key === 'Enter' || event.key === ' ') {
+ // Prevent the browser from scrolling down when Space is pressed
+ if (event.key === ' ') {
+ event.preventDefault();
+ }
+ toggleCollapsedVal();
+ }
+ };


Please add annotation to this callback

Applied in ff7fb87

hoxyq · 2026-06-23T12:31:17Z

Also, please see failed Flow jobs, you can reproduce it locally with yarn flow dom-browser.

Kertsu · 2026-06-26T01:13:39Z

Thanks for highlighting the issue! Can we just put the WhatChanged and badges in a sticky subheader, same like we do it for the component name?
Without any expand / collapse mechanics, I think that should address the issue?

Thanks for the feedback, @hoxyq!

Yes, that was my original instinct too. Just lift WhatChanged and the badges out of the scroll container so they sit above the commit list as a static subheader.

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That said, I understand this adds interaction complexity that may not be in line with the existing DevTools patterns. Happy to drop it and go with the simpler non-collapsible sticky subheader if you think the tradeoff is acceptable.

Just want to make sure we're aligned before I push another revision.

hoxyq

The reason I added the collapse mechanic is for cases where WhatChanged becomes tall, e.g. when a component has many changed hooks or props, the subheader can take up a significant portion of the sidebar height, leaving little room for the commit list. The collapsible lets users trade that context off for more list space when they need it.

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

hoxyq · 2026-07-06T14:08:00Z

Could you please attach a screenshot / screencast of the new behaviour?

Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Kertsu · 2026-07-06T15:38:02Z

That should be fine as long as the whole view is scrollable. If the user wants to see the full commit list, they can scroll. Essentially, the main information in this UI is what caused the render and component's information, the commit list is secondary.

Ooh okay, I see. Thanks for this. Will be making some changes!

Kertsu · 2026-07-06T15:38:30Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

Yup, sure. Thanks for the reference.

Kertsu · 2026-07-06T18:09:49Z

Could you please attach a screenshot / screencast of the new behaviour?
Also, if possible, please add an e2e test that will cover this new UI. You can find examples in react-devtools-inline/__tests__/__e2e__.

For the badges and what changed, I just used dummy data for manual testing. This is how it looks like. Let me know what you think, @hoxyq 🙌🏻

with.commit.list.container.mov

Previously, WhatChanged and InspectedElementBadges were rendered in the same scrollable container as the commit list. When a component had many render timestamps, scrolling through the commit history also scrolled the render summary out of view, requiring users to repeatedly scroll back to regain context. This change separates the render summary from the commit history by making only the commit list scrollable. WhatChanged and InspectedElementBadges remain fixed at the top of the sidebar while the render timestamps scroll independently, keeping the currently selected commit's context visible throughout navigation without additional interaction. Closesreact#36525 References: - https://github.com/facebook/react/blob/main/packages/react-devtools-shared/src/devtools/views/Profiler/SidebarSelectedFiberInfo.js#L132-L149

hoxyq

Thanks!

hoxyq

Thanks!

Kertsu · 2026-07-07T13:23:36Z

Thanks, @hoxyq! This is my first-ever meaningful contribution to an open source project as iconic as React 🚀

meta-claBot added the CLA Signed label Apr 9, 2026

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch 3 times, most recently from 377ecab to fed7c37Compare April 11, 2026 05:38

Kertsu changed the title ~~Add sticky header to SidebarSelectedFiberInfo~~[DevTools] Fix WhatChanged scrolling out of view in profiler sidebarApr 11, 2026

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch 2 times, most recently from 2f354f0 to 632176dCompare April 12, 2026 07:18

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch 3 times, most recently from 0a0376c to 162b730Compare April 25, 2026 07:51

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch 2 times, most recently from 4644160 to 80f014aCompare May 3, 2026 23:51

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch 2 times, most recently from 8e40685 to 8bb467fCompare May 14, 2026 06:46

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch 3 times, most recently from 1298a24 to d5ba16eCompare May 27, 2026 23:24

hbrooks mentioned this pull request May 28, 2026
[DevTools] Fix WhatChanged scrolling out of view in profiler sidebar ellipsis-dev-test/react#11
Open

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch 2 times, most recently from ddcda66 to 7027ebaCompare June 5, 2026 08:12

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch 2 times, most recently from 4723b2c to 2ecadebCompare June 16, 2026 01:21

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch from 2ecadeb to 4fdf488Compare June 23, 2026 12:22

hoxyq self-requested a review June 23, 2026 12:26

hoxyq requested changes Jun 23, 2026
View reviewed changes

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch from 4fdf488 to ff7fb87Compare June 26, 2026 02:07

Kertsu requested a review from hoxyq June 28, 2026 07:28

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch 2 times, most recently from d1d15d2 to 0645d41Compare July 2, 2026 06:06

hoxyq reviewed Jul 6, 2026
View reviewed changes

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch from 0645d41 to 2b51ab3Compare July 6, 2026 18:06

Kertsu force-pushed the feature/revamp-sidebar-selected-fiber-info branch from 2b51ab3 to 09d39aaCompare July 7, 2026 01:17

hoxyq approved these changes Jul 7, 2026
View reviewed changes

hoxyq merged commit 91cd812 into react:mainJul 7, 2026
238 checks passed

vercel-release-bot mentioned this pull request Jul 7, 2026
Upgrade React from 23def8fd-20260706 to 12a4baec-20260707vercel/next.js#95581
Merged