[BUG] : Add a "Back to Top" button for improved navigation on long pages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 63/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- css, javascript
- Domain
- frontend
Research direction
Find the landing page entry point and read how it handles scrolling and page styles. Add a floating button that appears after scrolling down, stays at the bottom-right, and smoothly returns the page to the top; hide it when the page is at the top. Verify the visibility threshold, placement, and scroll behavior on the long landing page.
Written by the indexing model from the issue text.
Description
Description
Feature Request
The landing page is relatively long, requiring users to scroll through multiple sections before reaching the footer. Once at the bottom, users must manually scroll back to the top to access the navigation bar.
Adding a "Back to Top" button would improve navigation and enhance the overall user experience.
Expected Behavior
- Display a floating Back to Top button after the user scrolls down a certain distance (e.g., 300–500px).
- Position it in the bottom-right corner of the screen.
- Clicking the button should smoothly scroll the page back to the top.
- Hide the button when the user is already at the top of the page.
Benefits
- Improves navigation on long pages.
- Reduces unnecessary scrolling.
- Enhances accessibility and overall user experience.
- Matches the behavior commonly found on modern websites.
Suggested Implementation
- Add a floating action button using
position: fixed. - Use
window.scrollTo({ top: 0, behavior: "smooth" })for smooth scrolling. - Show the button only after the user has scrolled beyond a predefined threshold.
- Dominant language
- Kotlin
- Stars
- 760
- Forks
- 122
- Avg merge
- 15h 3m
- Merged PRs (30d)
- 62
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ProdigyV21/ARVIO
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ProdigyV21/ARVIO#832 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ProdigyV21/ARVIO#367 · 1 comment ·
Maintainers usually reply within 1 day
-
[FEATURE]: pcOpentype:feature
Difficulty 4/5 3-5 days Newbie friendliness 15/100
ProdigyV21/ARVIO#831 ·
Maintainers usually reply within 1 day
-
type:bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
ProdigyV21/ARVIO#815 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
ProdigyV21/ARVIO#773 ·
Maintainers usually reply within 1 day
All issues in ProdigyV21/ARVIO
Similar issues
-
afk-ok area:frontend size:S
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
enorm-labs/event-junkie#4154 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PixelPlayerHQ/PixelPlayerOSS#193 ·
Maintainers usually reply within 1 day
-
bug web-server
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jooby-project/jooby#4035 ·
Maintainers usually reply within 1 day
-
Android: theme prop is ignored in R8-minified release builds (Theme enum is not Enumerable)Possibly taken @1kuko3 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
keiyoushi/extensions-source#20494 · 1 reaction ·
Maintainers usually reply within 1 day