# CSS loading fails on hotlinks from a Discourse forum

**URL:** <https://meta.discourse.org/t/css-loading-fails-on-hotlinks-from-a-discourse-forum/385067>\
**Category:** Support\
**Created:** [October 8, 2025, 6:43pm UTC](https://meta.discourse.org/t/css-loading-fails-on-hotlinks-from-a-discourse-forum/385067 "2025-10-08T18:43:13Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![emyoulation](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/emyoulation/32/165545_2.png) [@emyoulation](https://meta.discourse.org/u/emyoulation)\
**Post date:** [October 8, 2025, 6:43pm UTC](https://meta.discourse.org/t/css-loading-fails-on-hotlinks-from-a-discourse-forum/385067/1 "2025-10-08T18:43:13Z")

</div>

We are seeing a new odd behavior for hotlinks to a streamlit.app when posted to our support forum. When browsing (via Firefox, have not tested other browsers) to a hotlinked application, the CSS on the destination site is _not_ loading. The Discourse generated preview _does_ render the CSS.

When we paste the URL into the address bar (or browsing from a hotlink on a MediaWiki page), the CSS loads and it (the buttons and drag’n’drop hotzones) work.

(Not germane to the problem but… the streamlit app is a file format converter. Taking a genealogy data file in the GEDCOM text format and converts them to the Gramps XML text format.)

The behavior is described in more detail (including screen captures) at:  
[`https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781/14`](https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781/14)

The hotlink, posted as markdown and bare.

[`https://gramps-gedcom7.streamlit.app/`](https://gramps-gedcom7.streamlit.app/)

> **[Streamlit](https://gramps-gedcom7.streamlit.app/)**
>
> A GEDCOM 7 import library for Gramps.

---

_[View the full topic](https://meta.discourse.org/t/css-loading-fails-on-hotlinks-from-a-discourse-forum/385067)._
