Feature/portal 4.1 scroll position #399 #488
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dmytrotkk
requested changes
Mar 31, 2025
dmytrotkk
previously approved these changes
Jun 6, 2025
ines-SKALE
dismissed
dmytrotkk’s stale review
The merge-base changed after approval.
dmytrotkk
previously approved these changes
Jun 6, 2025
ines-SKALE
dismissed
dmytrotkk’s stale review
The merge-base changed after approval.
…/portal-4.1-scroll-position-#399
dmytrotkk
requested changes
Jun 10, 2025
…sion - Updated bun from v1.2.3 to v1.2.15 - Removed bun.lockb files from git tracking - Added bun.lockb to .gitignore to prevent future tracking - Regenerated lock files with new bun version
…skalenetwork/portal into feature/portal-4.1-scroll-position-#399
…/portal-4.1-scroll-position-#399
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
With this PR, the scroll position is now preserved when navigating back to a page.
For example: If a user scrolls to the bottom of the homepage, navigates to a dApp, and then returns, they will land back at the bottom of the homepage instead of the top.
Additionally, a floating “Go to Top” button has been added to the Ecosystem page, improving navigation and user experience.