Hover over filter scope indicator is transparent

[zuzana-vej]

Screenshot

Description

When yo hover over the filter indicator, the applied filters that appear over the chart are partially transparent - it makes is difficult to read. Previously background was white.

Design input

[describe any input/collaboration you'd like from designers, and
tag accordingly. For design review, add the
label design:review. If this includes a design proposal,
include the label design:suggest]

[dosubot]

The transparency you're seeing is actually intentional in the current code. The filter indicator popover background is set with 80% opacity in DetailsPanel/index.tsx:

color={`${theme.colors.grayscale.dark2}cc`}

The cc hex suffix equals ~80% opacity. If this was previously opaque (white background), the change likely happened during the theme migration to Ant Design tokens in PR #34732 or related theming PRs in mid-2025.

To fix this, the cc suffix could be changed to ff for full opacity, or removed entirely. The relevant files are:

• superset-frontend/src/dashboard/components/FiltersBadge/DetailsPanel/index.tsx
• superset-frontend/src/dashboard/components/FiltersBadge/Styles.tsx

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Mayankaggarwal8055]

Hi @zuzana-vej,

I’d like to work on this issue.

From initial investigation, it seems the transparency comes from the cc opacity in the filter indicator popover background. I’m planning to update it to full opacity (ff) to improve readability.

Please let me know if this approach works.

[Mayankaggarwal8055]

Hi @zuzana-vej @hainenber

I’ve submitted a fix for this issue: #38743

[fowlerp397-tech]

It looks like the transparency issue in the filter indicator was due to an 80% opacity setting (cc suffix), which was likely introduced during a theme migration. Changing the opacity to ff for full opacity seems like a good fix for improving readability. It’s great that a fix has already been submitted—hopefully that resolves the issue!

…

On Thu, Mar 19, 2026, 7:43 AM Mayank Aggarwal ***@***.***> wrote: *Mayankaggarwal8055* left a comment (apache/superset#38727) <#38727 (comment)> Hi @zuzana-vej <https://github.com/zuzana-vej> @hainenber <https://github.com/hainenber> I’ve submitted a fix for this issue: #38743 <#38743> — Reply to this email directly, view it on GitHub <#38727 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B72HASKCRLT2CO4NJ3SJNKT4RPTPLAVCNFSM6AAAAACWWZW4I2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBZHA3TGNZVGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>