Bug description

Since the upgrade to Superset 5.0.0, we’ve noticed a regression in number formatting for tooltips across multiple chart types.

Bug description In tooltips, the percentage value is glued to the number without any spacing or separator, making large numbers unreadable.

Example: Instead of: 1,143,922 — 100% we see: 1,143,922100.00%

This occurs across multiple chart types (e.g. Pie, Bar) and seems to affect all tooltips where both absolute and percentage values are shown.

Screenshot – See attached Image Image Image

Expected behavior Tooltip values should be properly formatted, e.g.: 1,143,922 — 100.00%

Superset version Superset 5.0.0

Browser: Chrome / MacOS

Screenshots/recordings

No response

Superset version

5.0.0

Python version

3.11

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

  • [x] 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.
  • [x] 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]

Hi @alex-webtense! I'm Dosu and I’m helping the superset team.

This is a known regression in Superset 5.0.0, caused by a new XSS filter that strips inline styles and whitespace from tooltip HTML, resulting in the percentage sticking to the number without spacing across multiple chart types. The issue is tracked in several GitHub issues (#33865, #33913) and was addressed by PR #34018, which updates the XSS filter to allow style attributes on table elements and restores proper tooltip formatting. This fix was merged on July 3, 2025 and will be included in the next release after 5.0.0.

As a temporary workaround, you can add custom CSS to your dashboard to add spacing to table elements in tooltips, for example:

table * {
  padding: 5px;
}

For a more robust solution, keep an eye out for the next Superset release that includes the merged fix. If you need an immediate fix, you can patch the XSS filter locally by allowing the style attribute on table-related tags as shown in the PR diff. More details and discussion are available in the linked issues and PRs.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X