Repository navigation
UI Overlap and Inconsistent Chart Display in Dashboard Layout #35080
Description
Bug description
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
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.
Activity
dosubot commentedon Sep 10, 2025
Recent changes on master/latest-dev have refactored dashboard layout components and grid logic, including margin normalization and intersection observer updates for chart rendering. These updates may have introduced new layout bugs or regressions that could cause UI overlap or inconsistent chart display in dashboards. Issues like chart/legend overlap (especially with ECharts), sticky UI elements covering controls, and malformed dashboard layouts have been reported before—workarounds include enabling legend scrolling in chart options, adjusting container heights or scroll regions for sticky elements, and exporting dashboard JSON to check for layout corruption or cycles [source]source]source]source]source].
If you’re seeing overlap or inconsistent rendering, try:
Recent UI changes may still be stabilizing, so monitoring for further upstream fixes or testing with different chart types/layouts could help narrow down the cause.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
msyavuz commentedon Sep 10, 2025
Can you give a bit more context on the issue? Does this happen on bigger screens etc?
rusackas commentedon Nov 18, 2025
If we can't get any more context here (I haven't run into this one, personally) we'll have to close this issue.
rusackas commentedon Jun 19, 2026
We can't act on this without more detail, e.g. screen size, dashboard layout, and steps to reproduce would help. Closing for now, but please reopen with that context and we'll investigate.