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

Heatmap visualizations don't adjust color values for dark mode #97636

Closed
Tracked by #184459
cchaos opened this issue Apr 20, 2021 · 13 comments
Closed
Tracked by #184459

Heatmap visualizations don't adjust color values for dark mode #97636

cchaos opened this issue Apr 20, 2021 · 13 comments
Labels
enhancement New value added to drive a business result Feature:ElasticCharts Issues related to the elastic-charts library Feature:Heatmap Heatmap visualization 🧊 iceboxed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@cchaos
Copy link
Contributor

cchaos commented Apr 20, 2021

The color schemas that render the heat map visualizations don't take into account whether they're in light or dark mode. So their fill color is exactly the same in both modes. This leads to misleading representation of the data since the lesser value squares are now the brightest.

Screen Shot 2021-04-20 at 09 17 11 AM

Screen Shot 2021-04-20 at 09 18 33 AM

@cchaos cchaos added bug Fixes for quality problems that affect the customer experience Feature:Heatmap Heatmap visualization Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Apr 20, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@stratoula
Copy link
Contributor

stratoula commented Apr 20, 2021

@cchaos I suggest fixing this when we replace the vislib heatmap with the es-charts implementation
cc @timroes @markov00

@stratoula stratoula added the Feature:ElasticCharts Issues related to the elastic-charts library label Apr 20, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/datavis (Feature:ElasticCharts)

@flash1293
Copy link
Contributor

@cchaos In Lens we provide the EUI palettes as well (as categorical colors for now, but soon we will use them in the same way as heatmap). I guess they will have the same issue. We have a central palette service - should it be theme aware and change the underlying palette? If yes, in all cases or just in cases like heatmap if the color is tied to an "intensity" variable of some sort?

@dej611
Copy link
Contributor

dej611 commented Apr 20, 2021

Need to consider this also for #95217 .

@cchaos
Copy link
Contributor Author

cchaos commented Apr 20, 2021

The EUI palette service has options to get darker or lighter or both so likely you just need to adjust to one direction or the other depending on the theme.

@flash1293
Copy link
Contributor

Ah perfect, we should just use that in the palette service - we can also do this on a separate PR @dej611

@markov00
Copy link
Member

If yes, in all cases or just in cases like heatmap if the color is tied to an "intensity" variable of some sort?

from https://www.carbondesignsystem.com/data-visualization/color-palettes for sequential monochromatic palettes:

In light themes, the darkest color denotes the largest values. In dark themes, the lightest color denotes the largest values.

@cchaos
Copy link
Contributor Author

cchaos commented Apr 20, 2021

Right so the discrete visualization palette's color values work in both light and dark mode (dark mode better actually). So there's nothing to change when using it to strictly denote different series. But when create single color (quantitative) palettes whose brightness and/or saturation correlates to a data value, this must change that starting value.

@timroes timroes added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Jul 22, 2021
@flash1293 flash1293 added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. enhancement New value added to drive a business result and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Oct 13, 2021
@gvnmagni
Copy link

gvnmagni commented Nov 2, 2021

Hi all! I would love to add a few things 🙂

TL:DR yes, we need to adjust color scales for dark theme inverting the lowest and highest value. We also need (future goal) to have a slightly adjusted palette for categorical values in order to increase contrast with background.

Long (-ish) explanation

You have already pointed out what I believe is the best behaviour for color scales on light and dark background. The basic concept is really simple, we convey values through the use of color and to do that we have to visually separate the shape from the background, it’s a matter of contrast. As the values represented increase we increase the color contrast using more intense color. For light background this means getting darker colours, for dark ones this means getting lighter.

Few additional considerations though.

Color palette for categorical data
The current discrete color palette is not affected by this matter since it does not convey numerical information, only categorical. This is true but at the same time it might be interesting to considerate a slightly different palette that could keep our current colours but increasing a little bit the contrast with the background, it could help legibility and accessibility.
This is what IBM does in this case, as a reference:

IBM Color palette

Color overlapping
This is a detail we have to take in consideration when overlapping shapes. It could happen (especially in maps, area charts, heatmaps...) that we want to show when two data series overlap and we want to highlight this. A common visual way as you surely know is to go with blending modes such as Multiply, where two colours get added. Problem is that these effect works differently on light and dark background since they interact with the background color as well

Light blending mode

Dark blending mode

So what we should do when we use these effect (if we use them, could be that we never use them) is to switch from Multiply to Screen as blending mode for dark backgrounds, this way the sum of colours will get lighter instead of darker

Sorry for the long post 🙂

@flash1293
Copy link
Contributor

That's awesome, thanks! About changing palettes based on theme: On the technical side I'm not 100% sure how we would handle this - could we store the original source palette as long as the user doesn't change any colors and automatically translate them based on the theme, @dej611 ?

@dej611
Copy link
Contributor

dej611 commented Nov 3, 2021

I think it is possible to handle default palette propagating palette name, which we store already in the configuration side.

@stratoula stratoula added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Feb 15, 2023
@timductive timductive added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Oct 18, 2023
@markov00
Copy link
Member

In order to provide better transparency of priorities, issues that will not be prioritized within the next 24 months are being closed.

Tracking request in Lens general improvements ice box #184459

@markov00 markov00 closed this as not planned Won't fix, can't repro, duplicate, stale May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:ElasticCharts Issues related to the elastic-charts library Feature:Heatmap Heatmap visualization 🧊 iceboxed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

9 participants