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

Add ability to customise inverse button colours #4043

Merged
merged 1 commit into from
Aug 9, 2023

Conversation

querkmachine
Copy link
Member

A "quick-fix" for the inverse button styles using hardcoded blue text and hover colours, where non-GOV.UK branded services probably want this to match the $govuk-brand-colour variable.

Related to #3918. Extracted from PR #3925, which includes more significant changes covering all inverse components.

Changes

  • Added public variable $govuk-inverse-button-background-colour, which defaults to govuk-colour("white").
  • Added public variable $govuk-inverse-button-text-colour, which defaults to $govuk-brand-colour.
    • This is probably technically a breaking change, as the inverse button's text colour was previously govuk-colour("blue"). This will look the same if the brand colour has not been changed, but will be different if it has.
  • Mapped the public variables to their scoped equivalents.

@querkmachine querkmachine self-assigned this Aug 4, 2023
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-pr-4043 August 4, 2023 08:52 Inactive
@querkmachine querkmachine force-pushed the inverse-button-improvements branch from 866240a to f4a74b3 Compare August 4, 2023 09:21
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-pr-4043 August 4, 2023 09:21 Inactive
@querkmachine querkmachine requested a review from a team August 4, 2023 09:23
@querkmachine querkmachine marked this pull request as ready for review August 4, 2023 09:50
Copy link
Contributor

@owenatgov owenatgov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💪🏻

@querkmachine
Copy link
Member Author

@owenatgov Can I get a quick reckon on whether this should be put down as a breaking change or not?

@owenatgov
Copy link
Contributor

@querkmachine So, based on your reasoning I reckon lets be cautious and call it a breaking change. We want teams to check that it's not going to impact their buttons, even if it's unlikely.

@querkmachine querkmachine force-pushed the inverse-button-improvements branch from f4a74b3 to 6b7178e Compare August 9, 2023 11:59
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-pr-4043 August 9, 2023 11:59 Inactive
@querkmachine querkmachine force-pushed the inverse-button-improvements branch from 6b7178e to c14f2c5 Compare August 9, 2023 12:05
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-pr-4043 August 9, 2023 12:05 Inactive
@querkmachine querkmachine merged commit c2cb81b into main Aug 9, 2023
@querkmachine querkmachine deleted the inverse-button-improvements branch August 9, 2023 14:26
@romaricpascal romaricpascal mentioned this pull request Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

3 participants