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:
Here's the same chart looking good once I hide the description:
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.
- [x] 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.
Comment From: dosubot[bot]
This appears to be a layout regression introduced after 4.1.2. The chart area in Superset is managed by flex layouts and dynamic resizing hooks, and the chart itself receives its size instructions independently of the description. There’s no evidence that the chart description directly changes the chart’s size or padding, so the x-axis cutoff is likely due to the parent container’s CSS—such as min-height, height, or flex settings—being squeezed when the description is visible. Ensuring that the chart container has enough height after accounting for the description, and avoiding overflow: hidden or insufficient min-height on critical containers, should help prevent the x-axis from being cut off. You may want to experiment with increasing the min-height or adjusting flex settings on the chart’s parent containers to see if that resolves the issue. If you’re using a custom chart plugin, also check its axis/padding logic, as that could contribute to the problem as well.
Reference: Chart and layout code
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: rusackas
Pinging @michael-s-molina even though I don't consider this a 5.0.0 blocker, but a 5.0.1 candidate.