Gradio web components failing to load

Thanks. I see. If it happens with that method too, this may connect to something beyond just Gradio itself:

The https://.hf.space/config part changes the picture quite a bit.

My previous guess was narrower:

src="https://<space-subdomain>.hf.space"
  → possibly failing through the by-subdomain lookup path

But if this also happens with:

<gradio-app space="<owner>/<space_name>"></gradio-app>

and the component repeatedly tries to fetch:

https://.hf.space/config

then this looks broader than only a by-subdomain reverse-lookup problem.

A literal empty-host URL like this:

https://.hf.space/config

suggests that the web component, or the Hugging Face Space metadata/config resolution path behind it, failed to resolve a valid .hf.space host at all.

So I would update the working hypothesis to something like this:

src="https://<space-subdomain>.hf.space"
  → may fail through by-subdomain lookup

space="<owner>/<space_name>"
  → may fail through owner/name → resolved Space host/config lookup

common layer:
  browser-facing Space identity/config resolution path

That is hard to explain as a bug inside the user Space runtime itself.

If the generated URL is literally:

https://.hf.space/config

then the missing value is probably the resolved Space subdomain / host, not something inside the Gradio app running in the Space.

Why this seems broader than the original repo-name hypothesis (click for more details) Why this may connect to the Spaces proxy / CORS thread (click for more details) Checks that may narrow it down (click for more details)

Short version: your space="<owner>/<space_name>" result makes this look less like only a repo-name-specific by-subdomain issue and more like a broader browser-facing Spaces integration problem.

Especially if the web component literally requests:

https://.hf.space/config

then something upstream failed to resolve the Space host before the request even reached the user app.