Users report that custom footers (and sometimes headers) added via Discourse’s theme components disappear or misrender when JavaScript is disabled—specifically in NoScript or Tor Browser’s “Safest” mode. adrelanos describes how their custom header appears below content and the footer vanishes entirely, even from page source. A temporary workaround involves duplicating footer HTML inside a <noscript> tag in the body, but they seek a proper fix. Canapin confirms the bug and reproduces it visually, showing the header misplaced and footer missing without JS. Canapin provides a minimal reproduction: adding red/green divs to header/footer components works with JS enabled but breaks without it—the footer doesn’t appear until scrolling, and scroll behavior glitches. merefield questions whether theme components are even intended to work without JS, suggesting the team clarify the level of noscript support. The issue appears tied to how Discourse renders theme components server-side versus client-side, and whether assets or DOM elements are injected correctly when JS is off. No official fix or statement is provided yet.
We’ve implemented both a custom header and footer for our forum by navigating to Settings > Customize > Themes > Components. Here, we installed the standard header component and associated it with the default theme. We then customized this component by adding our specific header HTML in the “Header” section and our footer HTML in the “Footer” section.
For regular users with JavaScript enabled, everything appears correctly with both the custom header and footer visible. However, when accessed with NoScript enabled, specifically using the Tor Browser at its “Safest” setting, the custom header gets misplaced below the content, while the custom footer disappears entirely—it’s also missing from the page source code.
As a temporary solution, we’ve integrated a noscript tag within the “Body” section of the component and embedded the custom footer HTML again inside this noscript tag. However, this is just a workaround, and we’d prefer a cleaner solution, with less likelihood of breaking in the future.
Bug report / feature request:
Ensure the custom footer is visible and rendered appropriately for NoScript users.
For the NoScript version, the header should appear above the content, and the footer should follow the content, mirroring the display sequence of the regular JavaScript-enabled page.
The footer part seems a bit glitchy. It should appear without having to scroll down, and the scroll behavior is weird, it’s like the scrolling motion is slowed down when we reach the custom footer. It might need an new topic as it’s maybe not related to the current issue.
In the Browser dev tools (Chrome), go to (Settings) on the right, then Preferences tab, then check “Disable Javascript”: