Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Add a scroll back to top button #168

Open
1 task done
Riddhi9570 opened this issue Apr 4, 2023 · 4 comments
Open
1 task done

[Feature] Add a scroll back to top button #168

Riddhi9570 opened this issue Apr 4, 2023 · 4 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@Riddhi9570
Copy link

Problem

There is no scroll back to top button in the CC Resource Archive page.

Description

I want to add a scroll back to top button at the bottom of the CC Resource Archive page. In case the number of resources is high and the user scrolls down much, this feature will help them to scroll back to top easily.

Implementation

  • I would be interested in implementing this feature.
@Riddhi9570 Riddhi9570 added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Apr 4, 2023
@Xaid-vfx
Copy link
Contributor

Xaid-vfx commented Apr 5, 2023

Hey @Riddhi9570,
I think this could actually be quite useful until Pagination or similar functionality is implemented. #24 is a discussion which focuses on implementing these technologies. Let's see what maintainers think about this. Also, which page exactly are you planning to add this button?

@kmr-sahil
Copy link

I can contribute to develop this feature, could you please assign me for this task !!!

@possumbilities possumbilities added 🏁 status: ready for work Ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Mar 8, 2024
@BalrajDhakad
Copy link
Contributor

I want to work on this issue @possumbilities

@SamarthShukla17
Copy link

@possumbilities I have created a PR #216 to resolve the issue. Kindly review it and provide any feedback. Thanks.❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Status: Backlog
6 participants