Inter not loading/rendering in Superset version 6.0.0 causing the web app to use a fallback font

[Gradsta]

Screenshot

Notice the rendered font section in the bottom right of the screenshot above.

Description

In Superset 6.0.0, Inter doesn't appear to load/render causing the application to use one of the fallback fonts (Helvetica on my machine). I first noticed this when upgrading my custom Superset Dockerfile to use apache/superset:6.0.0 as the base image, but I can also reproduce it using one of the official Docker Compose files included in the Superset repository: TAG=6.0.0 docker compose -f docker-compose-image-tag.yml up. I have also reproduced the issue on two different machines.

Note: Running the same command but with tag 5.0.0 doesn't exhibit the same problem—Inter loads and renders just fine.

Design input

N/A

[dosubot]

Hi @Gradsta! I'm Dosu and I’m helping the superset team.

This is a known issue in Superset 6.0.0: the Inter font won't load unless the @fontsource/inter package is present and imported in the frontend build. In 6.0.0, the Docker build process relies on frontend source imports to include fonts—there's no explicit step to package or copy font files beyond what's in the source code. If @fontsource/inter is missing from package.json or not imported in the theme source, the Inter font CSS won't be bundled, and you'll see fallback fonts like Helvetica instead. This is a change from 5.0.0, where font handling may have differed.

To fix this, add @fontsource/inter as a dependency in superset-frontend/package.json and ensure it's imported in your theme file (e.g., Theme.tsx). Then rebuild the frontend assets. If you're using a custom theme or loading Inter from a CDN, make sure your Content Security Policy (CSP) allows the font source, or the browser will block it. More details and related discussions are available in this issue and this discussion.

If you want to check if the font is being loaded, inspect the built static assets for Inter font CSS and look for any font loading errors in your browser's network tab.

To reply, just mention @dosu.

---

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

   

[dheeraj12347]

Hi, I’d like to work on this issue.
My plan is to ensure Inter is bundled correctly in the 6.0.0 frontend by adding @fontsource/inter to superset-frontend/package.json (if needed) and importing it in the main theme/entry file, then verifying that the Inter font actually loads in the built UI.
If this sounds good, I’ll open a PR with the change and screenshots.

[rusackas]

@msyavuz I seem to remember someone at Preset opening a PR that moved the font packages around for theming reasons. Perhaps related?

[dheeraj12347]

Hi, I’m trying to reproduce and fix #37226 locally, but I’m blocked on pulling the Superset Docker image. I’m on Windows with Docker Desktop, and even after switching from my college network to a personal hotspot and successfully pulling postgres:15, running docker compose -f docker-compose-image-tag.yml up (with x-superset-image changed to apache/superset:${TAG:-latest-dev} and TAG=6.0.0) still fails while pulling apache/superset:6.0.0 with errors like:

failed to copy: httpReadSeeker: failed open: failed to do request: Get "https://production.cloudflare.docker.com/...": http: server gave HTTP response to HTTPS client
and earlier: remote error: tls: protocol version not supported.

Would you recommend that I (1) switch to running the stack inside WSL2 Ubuntu and develop from there, or (2) use a different approach to reproduce 6.0.0 locally (e.g., a specific dev Dockerfile or a non-Docker setup) for this font issue? If there is a documented or preferred local dev path for contributors on Windows for 6.0.0, I’d really appreciate a pointer.

[dheeraj12347]

Hi, I noticed this issue now has an assignee and wanted to clarify how I should proceed. I had expressed interest in working on it and have started setting up a local 6.0.0 environment, but I’m running into Docker networking/TLS problems on Windows that are blocking me from pulling the apache/superset:6.0.0 image.
If the assignee is already actively working on a fix, I’m happy to step back and pick up another issue. Otherwise, I can continue and switch to a WSL2-based dev setup (or whatever you recommend for Windows contributors) and open a PR once I have the environment working.
Please let me know whether you’d like me to continue on this issue or focus on a different one.