Chrome Color Picker styling issues

[yuanworks]

The popup color picker (aka. Chrome Picker) has CSS styling issues.

Steps To Reproduce

1. Go to a new Paragraph Block
2. Select the background / font color
3. Choose a custom color

Issues

1. Width of the Chrome Picker is not the same as the parent popup component.
2. ChromePicker is using "Menlo" font by default, which is defaulting to a sans-serif font on Windows (ideally should just use the font-family: inherited which doesn't break the layout)

Screenshot

Desktop (please complete the following information):

• OS: Mac, Windows
• Browser Chrome, Firefox

Smartphone (please complete the following information):

• Device: Android

If there's a green light on this, I will work on a PR for it.

[ajitbohra]

styling issues have been fixed in the master branch

#5962 (comment)

[danielbachhuber]

@yuanworks Can you create a pull request for issue 2?

ChromePicker is using "Menlo" font by default, which is defaulting to a sans-serif font on Windows (ideally should just use the font-family: inherited which doesn't break the layout)

[yuanworks]

@ajitbohra for some reason I still see the wrong picker width after pulling from master on localhost, on the just-released 2.9.1 on a test site, as well as on https://testgutenberg.com/ (I'm aware that's running 2.8, but this issue seems to have been fixed some time ago).

Am I missing some other step after git pull origin? (other than npm install / npm run dev)

[pento]

@yuanworks: I can reproduce the same bug locally, #5962 was closed without being merged, so it hasn't actually been fixed.

[yuanworks]

Thanks @pento. Regarding the second issue I noted, Menlo is I believe a strictly MacOS font, and on Windows seeing the default serif Times New Roman font is an eyesore; it doesn't have as quick of a fix as the width though.

Should I try to contact the author of the component (not sure if Gutenberg is always keeping up with their latest version) so that he can hard-code something like font-famiy: Menlo, sans-serif to the component or it's better just to wait and see if the component will be rebuilt?

[pento]

Hrrm, that's a problem. It's worth contacting the author, but as @mtias suggested in #6863, we may need to rebuilt the colour picker, anyway.