Bug description
We are experiencing a graphical rendering issue with a Treemap chart in Apache Superset.
Some of the Treemap tiles display an unexpected thin vertical white/light line inside the colored area. The line appears as an internal separator even though the tile should have a continuous background.
The issue can be clearly seen, for example, in the tiles:
Arte Contemporanea
Architettura
I have attached a screenshot where the issue is highlighted with red arrows.
Expected behaviour
Each Treemap tile should be rendered as a continuous colored rectangle, without internal separator lines unless they correspond to an actual hierarchy/subcategory.
Actual behaviour
A thin vertical white line is rendered inside some tiles, visually splitting the rectangle and affecting the readability and appearance of the chart.
The issue appears to be related to the graphical rendering of the Treemap rather than to the data itself.
Could you please check whether this is a known issue with the Treemap visualization and whether it can be fixed or avoided through the chart configuration?
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.11
Node version
16
Browser
Chrome
Additional context
No response
Checklist
Bug description
We are experiencing a graphical rendering issue with a Treemap chart in Apache Superset.
Some of the Treemap tiles display an unexpected thin vertical white/light line inside the colored area. The line appears as an internal separator even though the tile should have a continuous background.
The issue can be clearly seen, for example, in the tiles:
Arte Contemporanea
Architettura
I have attached a screenshot where the issue is highlighted with red arrows.
Expected behaviour
Each Treemap tile should be rendered as a continuous colored rectangle, without internal separator lines unless they correspond to an actual hierarchy/subcategory.
Actual behaviour
A thin vertical white line is rendered inside some tiles, visually splitting the rectangle and affecting the readability and appearance of the chart.
The issue appears to be related to the graphical rendering of the Treemap rather than to the data itself.
Could you please check whether this is a known issue with the Treemap visualization and whether it can be fixed or avoided through the chart configuration?
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.11
Node version
16
Browser
Chrome
Additional context
No response
Checklist