Fix fonts loading

[dawoodkhan82]

Description

Fixes system fonts not loading properly

Closes: #(issue)

🎯 PRs Should Target Issues

Before your create a PR, please check to see if there is an existing issue for this change. If not, please create an issue before you create this PR, unless the fix is very small.

Not adhering to this guideline will result in the PR being closed.

Tests

1. PRs will only be merged if tests pass on CI. To run the tests locally, please set up your Gradio environment locally and run the tests: bash scripts/run_all_tests.sh

2. You may need to run the linters: bash scripts/format_backend.sh and bash scripts/format_frontend.sh

[gradio-pr-bot]

🪼 branch checks and previews

•	Name	Status	URL
	Spaces	ready!	Spaces preview
	Website	ready!	Website preview
🦄	Changes	detecting...

---

Install Gradio from this PR

pip install https://gradio-pypi-previews.s3.amazonaws.com/6d890c3dcad56e67d9d84dc5a35c23fd15db377f/gradio-5.8.0-py3-none-any.whl

Install Gradio Python Client from this PR

pip install "gradio-client @ git+https://github.com/gradio-app/gradio@6d890c3dcad56e67d9d84dc5a35c23fd15db377f#subdirectory=client/python"

Install Gradio JS Client from this PR

npm install https://gradio-npm-previews.s3.amazonaws.com/6d890c3dcad56e67d9d84dc5a35c23fd15db377f/gradio-client-1.8.0.tgz

Use Lite from this PR

<script type="module" src="https://gradio-lite-previews.s3.amazonaws.com/6d890c3dcad56e67d9d84dc5a35c23fd15db377f/dist/lite.js""></script>

[gradio-pr-bot]

🦄 change detected

This Pull Request includes changes to the following packages.

Package	Version
gradio	patch

• Maintainers can select this checkbox to manually select packages to update.

With the following changelog entry.

Fix fonts loading

Maintainers or the PR author can modify the PR title to modify this entry.

Something isn't right?

• Maintainers can change the version label to modify the version bump.
• If the bot has failed to detect any changes, or if this pull request needs to update multiple packages to different versions or requires a more comprehensive changelog entry, maintainers can update the changelog file directly.

[aliabid94]

This did not work for me. Try

import gradio as gr

with gr.Blocks(theme=gr.themes.Monochrome()) as demo:
    name = gr.Textbox(label="Name")
    greet_btn = gr.Button("Greet")

if __name__ == "__main__":
    demo.launch(ssr_mode=True)

and then also with ssr_mode=False and you'll see the fonts don't load when ssr_mode=True

[dawoodkhan82]

@aliabid94 Where are you seeing that the fonts don't load? i don't see any console errors, and the fonts look the same to me in both ssr and non-ssr modes. (Although I only see the fonts load in front end built mode, not dev mode)

[anirbanbasu]

@aliabid94 Where are you seeing that the fonts don't load? i don't see any console errors, and the fonts look the same to me in both ssr and non-ssr modes. (Although I only see the fonts load in front end built mode, not dev mode)

@dawoodkhan82
You won't see any errors in the output of the Gradio app. However, if you inspect the element in the web browser's console, here's how it would look like.

Clearly, the computed CSS is asking to load the correct font but the browser is rendering with a different font.

[anirbanbasu]

@abidlabs, as an aside but related to ssr_mode, the environment variable GRADIO_SSR_MODE is not documented in https://www.gradio.app/guides/environment-variables but referenced on these two lines:

gradio/gradio/blocks.py

Line 2460 in 3a6151e

else os.getenv("GRADIO_SSR_MODE", "False").lower() == "true"

and

gradio/gradio/routes.py

Line 1621 in 3a6151e

else os.getenv("GRADIO_SSR_MODE", "False").lower() == "true"

.

As yet another aside, the once SSR mode is enabled, a node server is started along with the Gradio server. However, at least on macOS (15.1.1), if I press Ctrl+C to stop the Gradio server, it keeps on waiting indefinitely to terminate the node process (with a message Stopping Node.js server...) and keeps waiting.

These should be addressed as separate issues, I guess.

[anirbanbasu]

These should be addressed as separate issues, I guess.

Opened issues #10138 and #10139