Can you still repro this? Atm I can’t locally.
Horizon uses the full-width component, so if you would use Foundation (full-width) theme, you’d see the same I think.
So while I agree it isn’t the best-looking layout, this is currently expected for all themes that use a full-width layout yes.
Screenshots provided shows it’s different in Horizon and Foundation 
Or am I missing something?
Oh! Need to check that. Didn’t know there was a distinction!
I don’t seem to have installed Foundation full-width, tried searching on meta and didn’t come up?
Its not a specific theme, it’s this component: Discourse Full-width component
2 Likes
We’re currently using the Custom Header Links theme component. I don’t imagine it’s a deal-killer for us but I’d just like to get a sense of whether or not it’s being considered for support – is it still under consideration for Horizon compatibility? Any guess how much work it would be?
1 Like
We’re currently not lining up any new compatibility work. Not saying it would never happen, but for any component compatibility to be added to the roadmap, it depends on how many requests we get for it.
I’m not very sure but I think it might be doable. The main conflict will be with the welcome banner setting, which uses the same outlet. So, if either completely you disable that, or set it to:
I think it might work reasonably well out of the box.
1 Like
you can try this css in a theme component and include it in the horizon theme:
@use "lib/viewport";
// ** only apply to desktop and larger viewport sizes **
@include viewport.from(lg) {
.container,
.list-controls {
margin-inline: 0!important;
}
}
1 Like
hmm i can’t reproduce this on my iphone15 in latest chrome, safari or firefox.
what device and browser are you using? seems odd it is trying to load the excerpts there.
1 Like
I tested it in a desktop using Chrome browser. I simply set the screen size to match that of a phone using F12. When I refresh the page from the cache (Ctrl + F5), the problem persists.
Okay, maybe this issue will go away after a Chrome update (though I think I have the latest version). Oh well.
I have one more question. Why doesn’t that block with the tag selection and buttons hide when I scroll down? Is it just me, or does this happen to everyone? It takes up quite a bit of screen space; it would make sense to hide it when scrolling down.
2 Likes
that is apparently the expected behavior for horizon theme (probably to always show what category/tag the user is in?), but i agree that it takes up too much space to be anchored there when scrolling. looks like the category and tag breadcrumb selectors are inside the navigation-container.
2 Likes
On smaller phone screens, these two buttons take up a lot of space in the title list content.
I believe the trend in information density is toward greater compactness. My approach was to remove the fixed property for this row in CSS.
1 Like
yea that looks like expected behavior unfortunately. the pinned button and topic notifications buttons are outside the topic-footer-main-buttons div. not sure if it’s possible but those two buttons should at the very least be in their own row together, but it would definitely be more ideal if they could render inside the topic footer main buttons row here.
edit: Moin pointed out to me that this is because Horizon hides the text explainers (that i don’t usually pay attention to lol)
they can be displayed by using this CSS if one needs:
.notifications-button-footer .reason .text,
.pinned-button .reason .text {
display: inline-flex;
}
2 Likes