Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[React 18] Docs issues follow-up #7016

Closed
cee-chen opened this issue Aug 1, 2023 · 1 comment · Fixed by #7060
Closed

[React 18] Docs issues follow-up #7016

cee-chen opened this issue Aug 1, 2023 · 1 comment · Fixed by #7060
Assignees
Labels
task A task associated with a larger issue, wouldn't prioritize it independently

Comments

@cee-chen
Copy link
Contributor

cee-chen commented Aug 1, 2023

Page template jumping

Page template padding offset is lost and then restored on route navigation, leading to the page title jumping like below:

page_template

Sidenav scroll 'memory' is lost

Previous React 17 behavior - clicked links scroll into view in the center of the nav:

prod

React 18 behavior - scroll behavior is completely lost:

staging

The current scroll behavior requires a timeout of ~100ms to restore properly, which leads to visual jank on page navigation:

dev

@cee-chen cee-chen added the task A task associated with a larger issue, wouldn't prioritize it independently label Aug 1, 2023
This was referenced Aug 1, 2023
@cee-chen
Copy link
Contributor Author

cee-chen commented Aug 1, 2023

Cross-posting my thoughts in Slack for (maybe) helpfulness:

I could be wrong, but it feels like in React 17, our components didn't fully rerender between pages (which is the whole point of SPAs, imo) but now on in React 18, when a route changes, everything on the page is fully unmounting and remounting which is causing a bunch of visual jank

What I'm trying to figure out is if this is either 1. directly caused by React 18 changes, or 2. related to the React Router changes we made as part of the react 18 upgrade

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task A task associated with a larger issue, wouldn't prioritize it independently
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants