Open teresaalvarezsoler opened 4 days ago
Pinging @elastic/kibana-visualizations (Team:Visualizations)
Hi! Here are some naming suggestions for the new, and current, color palettes:
the 2 new palettes
the existing ones
The new ones don't get any temporality in the way they're named, to reinforce that they're the current best and latest. The older ones get renamed to add that temporality notion so that users know they're what they've seen/used in the past, in case they get nostalgic of the old days.
Let me know what you think and we can refine as needed.
@gvnmagni in the meeting this week it was mentioned to use prefers-contrast
. To me that would mean we have a user setting toggle, then we use this under the hood to pick the high contrast color palette based on the selected palette. Assuming not all palettes have a high contrast version, I don't know how/if we want to alert the user when the current palette does not support high contrast.
In this flow there would be no need for the explicit naming of the Elastic high contrast palette.
Description
The new color palette and the high contrast one need to be tested for all chart types to make sure they both work well for all edge cases.
Tasks
[ ] Include both palettes as additional options for terms
[ ] Replace all existing palettes for values with the new colors -- to ensure backwards compatibility, existing charts can keep their colors as
custom
[ ] Replace the colors in the color picker for dimensions
Testing
Test the following scenarios: