CSS loading fails on hotlinks from a Discourse forum

Product Support

AI-generated summary

emyoulation reports an issue where CSS fails to load on a Streamlit app (https://gramps-gedcom7.streamlit.app/) when accessed via hotlinks from their Discourse forum, specifically in Firefox. The CSS renders correctly in the Discourse preview and when the URL is manually entered or accessed from non-Discourse pages (e.g., MediaWiki). The app, a GEDCOM-to-Gramps XML converter, functions otherwise, and reloading the page resolves the CSS issue temporarily. tobiaseigen notes the topic received no replies, and emyoulation confirms no direct fix was found, though the issue is non-critical. They express concern that Firefox behaves differently depending on the referrer (Discourse vs. direct), calling it disconcerting. Further details and screenshots are available in the original post: GEDCOM 7 Library thread, post 14.

1

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

The hotlink, posted as markdown and bare.

https://gramps-gedcom7.streamlit.app/

2

Looks like your topic found no takers! Sorry about that. Were you able to resolve your issue in the meantime?

3

No direct resolution. If you reload the page, it loads the CSS. So it is not critical.

However, that Firefox delivers different content when linked from from Discourse is… disconcerting.