Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

New Component Request: Back to Top button

Open
  • Is something wrong?
#825 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 7 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
scss
Domain
design, frontend

Research direction

Start by reviewing the existing Neutral button styling linked in the issue and the design-system patterns for reusable components. Define the Back to Top behavior from the requirements: fixed lower-right positioning, delayed appearance after scrolling, responsive use, and light styling on both backgrounds. Done means the component meets these behaviors and remains unobtrusive on short pages.

Written by the indexing model from the issue text.

Description

Design 🎨
Please describe the use case(s) for this component

On a long page it is useful to have a quick navigate to top option. (see original bedrock issue: https://github.com/mozilla/bedrock/issues/9910)

The button should not appear on pages that are not long enough to need this option

Please provide any designs or previous implementations of the proposed component
back-to-top

potential to use Neutral button styling: https://protocol.mozilla.org/components/detail/button--neutral.html

Please describe what this component does in the following conditions

  • Dark or light background, stays light background and dark arrow up icon
  • When viewed in a mobile/responsive viewport: same positioning as desktop, about 1em from bottom right corner, position fixed & sticky (appears after user scrolls down about 1.5x viewport size)
Please provide examples of this type of component in use in non-Mozilla web properties

Image examples and general best practices here:
https://www.nngroup.com/articles/back-to-top/

  1. Use a Back to Top button for pages that are longer than 4 screens.
  2. Place a persistent Back to Top button in the lower right side of the page.
  3. Label the button Back to Top.
  4. Have one sticky Back to Top link per page instead of including multiple links in every section of the page.
  5. Keep the button small so it doesn’t cover important page elements.
  6. Make the button stand out visually on the page rather than blend in.
  7. Consider delaying the appearance of a Back to Top option until after users scroll a few pages AND indicate that they want to scroll up
  8. Make the button stationary.
  9. Let users control scrolling.
Is the development of this component a blocking dependency for other work? Please explain if so

Protocol team has come to consensus on need after discussion on longstanding bedrock issue. It is not blocking but would be a good UX improvement on pages such as https://www.mozilla.org/en-US/firefox/privacy/book/

Dominant language
SCSS
Stars
298
Forks
83
Avg merge
9d 7h
Merged PRs (30d)
7

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/protocol

All issues in mozilla/protocol

Similar issues

More Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.