-
Notifications
You must be signed in to change notification settings - Fork 59.6k
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
Add a go to top button #1894
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
@siddhantvirus Thanks for opening an issue! I'll triage this for the right team to take a look 👀 |
Is someone work on this issue? |
👋 @Ylan-sayada We don't have any design specs created for this issue 💛 If you're looking for somewhere to contribute, there are quite a few issues with a help wanted label ✨ |
@janiceilene could you please look into to why there are two random spammy comments on this issue from accounts which don't seem to have any actual activity whatsoever? |
This comment has been minimized.
This comment has been minimized.
@FREELANCEGITIT ? I'm sorry but i wasn't referring to you in any of my comments 😅 |
@siddhantvirus I'm not sure why that was happening, but they should all be removed and reported now 💛 |
Hi , Nice to meet you. Could I work on this issue with you?? If it would be good, what we will have to do is below? I would be happy to receive your reply!! |
Happy New Year , every one! |
Happened in #2243 |
What is the current behavior?
Currently, there are no buttons to let a reader scroll back to the Table of Contents on any page on docs.github.com.
While this can be bypassed by a desktop/laptop by using the home button, users using a mobile device do not have the same privilege
What changes are you suggesting?
I suggest adding a floating button on the bottom right corner at least the mobile view of the website which when clicked either takes the user back to the top of the page , or can be a linked to the href of the table of contents heading.
Additional information
I believe the approach needs to be such , that it can be enabled on only the pages with actual documentation and that it doesn't need to be manually added for every markdown page.
The text was updated successfully, but these errors were encountered: