Skip to content

ref(trace): migrate virtualizedViewManager off browserHistory#115927

Merged
evanpurkhiser merged 1 commit into
masterfrom
evanpurkhiser/ref-trace-migrate-virtualizedviewmanager-off-browserhistory
May 20, 2026
Merged

ref(trace): migrate virtualizedViewManager off browserHistory#115927
evanpurkhiser merged 1 commit into
masterfrom
evanpurkhiser/ref-trace-migrate-virtualizedviewmanager-off-browserhistory

Conversation

@evanpurkhiser
Copy link
Copy Markdown
Member

Add a public navigate field on VirtualizedViewManager and assign it from useTraceWaterfallModels (which calls useNavigate()). The FOV query-param sync now goes through it instead of the deprecated browserHistory shim.

The field is nullable so existing test constructors don't have to pass anything.

Add a public `navigate` field on `VirtualizedViewManager` and assign it from `useTraceWaterfallModels` (which calls `useNavigate()`). The FOV query param sync now goes through it instead of the deprecated `browserHistory` shim. The field is nullable so existing test constructors don't have to pass anything.
@evanpurkhiser evanpurkhiser requested a review from a team as a code owner May 20, 2026 18:24
@evanpurkhiser evanpurkhiser enabled auto-merge (squash) May 20, 2026 18:24
@evanpurkhiser evanpurkhiser requested review from a team and removed request for a team May 20, 2026 18:24
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 20, 2026
@github-actions
Copy link
Copy Markdown
Contributor

📊 Type Coverage Diff

✅ No new type safety issues introduced. Coverage: 93.57%

Copy link
Copy Markdown
Contributor

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 0fe4878. Configure here.

},
});
{replace: true}
);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing preventScrollReset on FOV replace navigation

Low Severity

The old browserHistory.replace() shim automatically passed preventScrollReset: true (see comment in browserHistory.tsx L76-78). The new navigate() call only passes {replace: true}, losing scroll-reset prevention. Since this fires on every debounced FOV change during panning/zooming, it may cause unwanted scroll jumps. Consider adding preventScrollReset: true to the options.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 0fe4878. Configure here.

@evanpurkhiser evanpurkhiser merged commit f585833 into master May 20, 2026
72 checks passed
@evanpurkhiser evanpurkhiser deleted the evanpurkhiser/ref-trace-migrate-virtualizedviewmanager-off-browserhistory branch May 20, 2026 18:52
JonasBa pushed a commit that referenced this pull request May 21, 2026
Add a public `navigate` field on `VirtualizedViewManager` and assign it
from `useTraceWaterfallModels` (which calls `useNavigate()`). The FOV
query-param sync now goes through it instead of the deprecated
`browserHistory` shim.

The field is nullable so existing test constructors don't have to pass
anything.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants