This thread discusses the Discourse Full-width component, an experimental theme component designed to make Discourse occupy the full browser width. chapoi introduces the component, noting it is currently used in the Fully theme and Meta’s “Default (full width)” theme. Users are warned that because it overrides widgets, it may break with header refactors or conflict with other components.
Common issues and solutions include:
Compatibility Errors:Diego_Santos reported errors after updating, which Arkshine resolved by advising a Discourse core upgrade to match recent component updates.
CSS Customization: To expand tables to full width within topics, thaidb asked for help; Arkshine provided CSS variables (--topic-body-width and --d-max-width) to override default constraints.
Sidebar Width:thaidb inquired about widening the sidebar for long category names, though no direct solution was provided in the excerpt.
Header Search:loginerror highlighted discrepancies between Safe Mode and the full-width component regarding header search behavior on small screens. lindsey confirmed a fix was merged to collapse the search bar into an icon on narrow widths.
Regarding support status, awesomerobot clarified that while bugs are addressed, the component remains experimental and is not guaranteed to work with all themes.
This is still an experimental component, which overrides widgets, will most likely break with header refactors, and will not play well with other header components.
We’ll do our best to maintain this component and to minimise breaking changes, but we can’t guarantee these will never occur. A fix will most likely come, but you may have to wait a bit longer.
it’s officially supported in that we’ll look at bugs that are reported, but it’s still experimental in the sense that it’s not something we expect to work well with all themes and theme components
Given the announcement over here, I wanted to point out some discrepancies in experience when using the Full Width component and the header search feature.
I assume at least the same experience should be the case, if not simply collapsing the header search to an icon for very low page widths (like on the mobile view).
We just recently merged a fix to ensure the header search bar collapses to the icon on small screen widths. Once you’ve updated Discourse, could you please take a look and let us know if that’s looking better?
This is still an experimental component, which overrides widgets, will most likely break with header refactors, and will not play well with other header components.
