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

Error Color mismatch between Figma and Production #3519

Open
2 of 6 tasks
jeana-adhoc opened this issue Nov 14, 2024 · 4 comments
Open
2 of 6 tasks

Error Color mismatch between Figma and Production #3519

jeana-adhoc opened this issue Nov 14, 2024 · 4 comments
Assignees
Labels

Comments

@jeana-adhoc
Copy link
Collaborator

jeana-adhoc commented Nov 14, 2024

Bug Report

  • I’ve searched for any related issues and avoided creating a duplicate issue.

What happened

I was comparing output between figma and staging/production and noticed the error colors are not the same.

What I expected to happen

I expected figma and production to be using the same color for error messages

Reproducing

  • Formation version:
  • Device: (e.g. iPhone 8, Macbook)
  • Browser: (e.g. Firefox, IE 11)

Steps to reproduce:

  1. Load a form on staging and trigger an error
  2. Load a figma file and recreate the component
  3. Load the figma component with an error
  4. See the color difference.

Here is a screenshot

Image

The image on the left is from staging, on the right is a brand new component built using VADS component library.

It looks like Figma is using vads-color-error whereas the code is using vads-color-error-dark.

Urgency

How urgent is this request? Please select the appropriate option below and/or provide details

  • This bug is blocking work currently in progress
  • This bug is affecting work currently in progress but we have a workaround
  • This bug is blocking work planned within the next few sprints
  • This bug is not blocking any work
  • Other

Details

Estimating

Designers:
Provide your estimate of 1, 2, 3, 5, 8 or 13
@babsdenney
@danbrady
@LWWright7

@jeana-adhoc jeana-adhoc added bug Something isn't working platform-design-system-team labels Nov 14, 2024
@caw310 caw310 added the Figma label Nov 14, 2024
@Andrew565
Copy link
Contributor

Andrew565 commented Dec 12, 2024

FWIW, it's not clear here if what needs to change is Figma or the component styles. I checked the va-checkbox component's error styling, and it's pulling from the .usa-error-message class, which is set at the same color as our vads-color-secondary-dark (see attached screenshot). We can easily override this color to whatever color we want, though, if we decide the component needs to change.

Image

@danbrady danbrady self-assigned this Dec 19, 2024
@danbrady
Copy link
Contributor

danbrady commented Jan 6, 2025

@babsdenney @LWWright7 This is ready for review.

The key point is that USWDS uses $theme-color-error-dark (#b50909) for error text, borders, etc., and not $theme-color-error (#d54309). See USWDS color tokens.

I took a look at all components that have an error state and updated any that used the vads-color-error token to use $vads-color-error-dark instead (which maps to the USWDS value).

These are the components that were updated:

  • Form Elements:
    • Label
    • Error Text
    • Hint Text
    • Label Header
  • Date Input
  • File Input
  • Memorable Date
  • Privacy Agreement
  • Radio Buttons
  • Select and Select Element
  • Statement of Truth
  • Text Input and Text Input Element
  • Textarea and Textarea Element

(This list is also in the publishing notes on the Form Elements page.)

Please let me know if I missed any. Thanks!

@LWWright7
Copy link
Contributor

These all look good to me!

@babsdenney
Copy link
Contributor

Everything looks good, just found one tiny spot using the old colors on memorable date (vertical error bar).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants