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
Selecting a version from the 'Showing stats for' dropdown causes the scrollbar to be reset to the top of the page. It would be nice if the page remained scrolled to the 'Stats' section after using the dropdown.
While this is a fairly minor issue, it can be somewhat annoying on pages with large READMEs, where where 'Stats' section is below the fold.
The text was updated successfully, but these errors were encountered:
I don't think there's any way we can actually "fix" this issue. Ultimately this boils down to some UI confusion. "Showing stats for" actually is navigating you to the page for a new version. We have no way of knowing ahead of time whether the height of that page (mainly determined by the README) will be the same, and going to the top of the page makes the most sense for navigation.
However, the wording of that dropdown strongly implies that it only affects the download stats, rather than the entire page. I'm not sure whether the right answer is to reword that drop down, remove it, or change it to only affect download stats.
Checking this issue out, I would also expect that the dropdown would select the version to display stats for, and not switch to a different version of the same crate.
My proposal would be to either remove the dropdown, or make it so that the dropdown only toggles the stats, which could be confusing for other reasons.
Uh oh!
There was an error while loading. Please reload this page.
Selecting a version from the 'Showing stats for' dropdown causes the scrollbar to be reset to the top of the page. It would be nice if the page remained scrolled to the 'Stats' section after using the dropdown.
While this is a fairly minor issue, it can be somewhat annoying on pages with large READMEs, where where 'Stats' section is below the fold.
The text was updated successfully, but these errors were encountered: