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

Update Button Style - Add Color Hover Support

Open
#784 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the button style definitions in the repository's SCSS and compare their default, hover, active, visited, and disabled states with the issue. Confirm the intended inverse blue and pink hover colors before editing; done means the documented button variants match the agreed states and work across relevant interactions.

Written by the indexing model from the issue text.

Description

Design 🎨 Dev ready ⚙️
Button Style - Add Color Hover Support
Use Cases
  • Support for Error & Success States
  • Support for future Brands
What is Changing?

Black Button

  • Default, Fill: #000000; Border: 2px solid black;
  • Hover, Active, Visited Fill: transparent; Border: 2px solid black;
  • Disabled Opacity: 80%;

Inverse Button - #0060DF, should be whatever color link blue is

  • Default, Fill: #ffffff; Border: 2px solid #0060DF;
  • Hover, Active, Visited Fill: #0060DF; Border: 2px solid Blue;
  • Disabled Opacity: 80%;

Red Button

  • Default, Fill: #EF4056; Border: 2px solid #901424;
  • Hover, Active, Visited Fill: #EF4056; Border: 2px solid #901424;
  • Disabled Opacity: 80%;

Pink Button - Subject to Change Hover

  • Default, Fill: #FF4AA2; Border: 2px solid #FF4AA2;
  • Hover, Active, Visited Fill: #FD007B; Border: 2px solid #FD007B;
  • Disabled Opacity: 80%;
Screen Shot 2022-05-17 at 10 27 43 AM
Dominant language
SCSS
Stars
298
Forks
83
Avg merge
9d 7h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

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.