apache/superset

"Show chart description" causes bottom of x-axis to be cut off heatmap in 5.0.0rc3

Closed

#33,737 opened on Jun 11, 2025

View on GitHubContributor guide
 (7 comments) (0 reactions) (0 assignees)TypeScript (17,291 forks)batch import
#bug:cosmetic#bug:regressiongood first issueviz:charts:heatmap

Repository metrics

Stars
 (72,837 stars)
PR merge metrics
 (Avg merge 31d 15h) (773 merged PRs in 30d)

Description

Bug description

The chart has plenty of room on the dashboard and I can see the x-axis fully when the description is hidden. But when I show it, the x-axis gets blocked:

Image

Here's the same chart looking good once I hide the description:

Image

This is a regression from 4.1.2 where this did not occur. Maybe only affects heatmap? Other chart types work as expected with description shown.

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Firefox

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Contributor guide

Research direction
Investigate the CSS or component layout that hides the chart description toggle. Check the heatmap chart's container height or overflow settings. Look at the difference between showing and hiding description to find what changes the layout.
Tech stack
javascripttypescriptreactnodejspython
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.jsnpm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70