This repository has been archived by the owner. It is now read-only.

Customizer Pimary Color: Hexidecimal input #613

Closed
josephdickson opened this Issue Nov 16, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@josephdickson
Copy link

josephdickson commented Nov 16, 2018

Feature Request

Problem: It's not possible to precisely select the Primary Color in the Customizer. Users have to slide back and forth then inspect with their browser and try to trap the specific color they might desire.

color slider

Desired Solution: Add a hexidecimal input box that can be used to override the color slider if desired.

Current work around: Use CSS to override colors manually in a Child Theme or the Additional CSS Customizer Box. However, this requires a lot of inspection and testing.

@kjellr

This comment has been minimized.

Copy link
Collaborator

kjellr commented Nov 16, 2018

Hi, @josephdickson — Thanks for the report.

Twenty Nineteen's original custom color implementation allowed for users to enter a Hex value, as shown in the GIF here:

47083306-78098680-d210-11e8-8a49-e18b08bf9cc7

This was problematic in that it opened the door to very inaccessible color combinations throughout the site. We looked into the addition of a color contrast checker to warn users about that, but ultimately abandoned that idea after considering the bulk and complexity it'd add to the theme.

In the end, we borrowed a solution from Twenty Seventeen, and implemented a color hue picker instead. This allows people to customize the color while also guiding them towards a more accessible palette.

Switching to a hex color picker isn't something @allancole and I are looking to change before the release at this point, but I could definitely imagine a separate plugin or child theme handling this sort of thing.

@kjellr kjellr closed this Nov 16, 2018

@kjellr kjellr added the wontfix label Nov 16, 2018

@josephdickson

This comment has been minimized.

Copy link

josephdickson commented Nov 16, 2018

That's a pretty good reason. Thanks for the reply.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.