Fix sidenav highlight issue #2502
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
| @knno is attempting to deploy a commit to the Docsify Team on Vercel. A member of the Team first needs to authorize it. |
| The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| Hi @knno |
| Hi @sy-records |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Summary
Hi
In this PR, the sidenav is fixed whenever it is scrolled and then main content is scrolled so that it doesn't lose it's scroll position.
It fixes the value of
isInViewandnotThanThere is a little problem when you scroll the page and see the sidenav highlighted item, it is automatically scrolled to top in the sidebar, this is distracting if the user scrolls the sidebar for a look or such, then continues to scroll in the main content.
Related issue, if any:
What kind of change does this PR introduce?
Bugfix
For any code change,
Does this PR introduce a breaking change?
No
Tested in the following browsers: