You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since 0.23, every (non-class) function is its own page. This makes it harder to see the documentation of multiple functions quickly (e.g. to skim through what a library has to offer) since the sidebar does not remember its scroll state between navigations, so you have to scroll down to the correct spot each time.
Example:
Here, I scrolled down to see SomeType.
After clicking it, the sidebar scrolled back up.
Suggested Solution
I can think of 2 ways to address this problem:
Don't change the scroll state of the sidebar if the sidebar's content doesn't change between navigations.
This is could be trivially implemented if something like React client-side routing were to be used. Of course, adding client-side routing would likely be non-trivial, but it would also have additional advantages (such as no page flickering during loads).
When loading the page, scroll the sidebar such that the current element is visible.
This is similar to the behavior of IDEs like VSCode that scroll to the currently selected file in their file explorer.
The text was updated successfully, but these errors were encountered:
Search Terms
theme, scroll, scroll state, side bar, sidebar
Problem
Since 0.23, every (non-class) function is its own page. This makes it harder to see the documentation of multiple functions quickly (e.g. to skim through what a library has to offer) since the sidebar does not remember its scroll state between navigations, so you have to scroll down to the correct spot each time.
Example:
Here, I scrolled down to see
SomeType
.After clicking it, the sidebar scrolled back up.
Suggested Solution
I can think of 2 ways to address this problem:
Don't change the scroll state of the sidebar if the sidebar's content doesn't change between navigations.
This is could be trivially implemented if something like React client-side routing were to be used. Of course, adding client-side routing would likely be non-trivial, but it would also have additional advantages (such as no page flickering during loads).
When loading the page, scroll the sidebar such that the current element is visible.
This is similar to the behavior of IDEs like VSCode that scroll to the currently selected file in their file explorer.
The text was updated successfully, but these errors were encountered: