fix: fixing menu when scrolling up #116
Open
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Nice work adi! However, It's good that the menu bar disappears when you scroll down. It should only 'scroll in' from the top when you scroll up. You see what I mean? |
2 similar comments
|
Nice work adi! However, It's good that the menu bar disappears when you scroll down. It should only 'scroll in' from the top when you scroll up. You see what I mean? |
|
Nice work adi! However, It's good that the menu bar disappears when you scroll down. It should only 'scroll in' from the top when you scroll up. You see what I mean? |
…rolling up and to hide when scrolling down
|
Hello, I have done some modification on the navigation bar with useEffect hook. Kindly check the code or the deployed code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the intended behavior that I have fixed.