Hi there, I used to inject my forum’s name as text into the header after the the logo, but it was messy to try to make it fit with all the combinations of browser widths and header content possibilities. So now I use a logo image with the actual logo followed by the forum name in the image itself.
But since updating to v2026.7.0 I’m having trouble making it fit at certain widths inside topics. (There’s no issue on the hompage as the header there has more empty space). The Discourse setting for the Small logo describes it as “The small logo image at the top left of your site, seen when scrolling down.” However, the actual behavior is a bit more complex than that. At browser widths >=1015 pixels (roughly) when scrolling down inside a topic with the sidebar visible the Primary logo is still used, which has to be shrunk to fit in the small remaining space to the left of the topic title, which makes it unreadable in my case. Then smaller widths than ~1015pixels makes it switch to the Small logo. Is there any way to make it always use the Small logo or even the Mobile logo when scrolling down in a topic view? There are some similar ideas in this old thread, but it’s not exactly what I’m looking to do and I’m not sure if the technical implementation still applies:
Or is this maybe a bug in the latest version in which it is incorrectly using the Primary logo when scrolling down inside a topic? Thanks in advance for the help.
// When the sidebar is visible, force the HomeLogo to be in an 'un-minimized' state.
const transformerExists = api.registerValueTransformer?.(
"home-logo-minimized",
({ value, context }) => {
if (value && context.showSidebar) {
return false;
}
return value;
}
);
^ And this one too, but it’s just for automated testing, correct?
Is there any reasonably clean way I can “override the override” without doing a full-blown fork of the component? I mainly need it because 1) many of my users have definitively expressed a strong preference for the wide layout, and 2) there are too many major and minor quirks that need to be handled with CSS rules in addition to just increasing the --d-max-width and --topic-body-width values. I’ve been maintaining my own theme component with a bunch of pure CSS rules that I copied and adapted from discourse-full-width-component/common/common.scss at main · discourse/discourse-full-width-component · GitHub, but it tends to break with each major Discourse release and I would prefer something better maintained and lower maintenance like the Full Width Component.
Nice!! Thanks so much Kris.
Will that commit be available for ESR? Currently it says my Full width component is Theme is up-to-date with d-compat/2026.7
