Alignment issue on ultrawides?
At 1920x1200
Is it really bad if I just visit for the forum, and donât particularly want to âreturnâ to the main site?
Nope.
I barely ever visit the main site.
The div containing the top navbar is set to a css class of container
. This has a breakpoint and will be full width on devices smaller than 1115px across but once its above that it no longer expands.
Itâs likely that all @kreestuh has to do is change it to container-fluid
to fix this.
Just tried that. Put the link all the way to the left. container-fluid
fills to 100% page width.
Semi misaligned on my 1366X768 display too, I would honestly rather see this banner removed.
There are ways of having a nice integrated header. See this site for example http://forum.driveonwood.com/
Changing the container
class to wrap
instead seems to fix it.
Anyone confirm that?
Looks good here.
Firefox, Linux, 1920x1200.
Interesting.
Also funny that the level1 name doesnât change to the correct colour. A different but
There you go [BUG] Logo is white.. on the white theme
Funny, I never noticed this because I never run a browser full-screen.
3440x1440 half screen:
3440x1440 full screen:
Havenât tested wrap
, but itâs this:
#top-navbar .container {
margin: 0 auto;
max-width: 1115px;
}
The Link-container has a max-width and gets centered, thatâs why ultrawide looks off.
You could also remove the class if you wanted to, since it doesnât do anything else.
I guess the idea is/was that itâs supposed to be centered along with the content, but then the logo/menu bar is kinda offâŚ
On a sidenote:
That bar has been missing on the mobile site for pretty much forever.
IMO it would be better off in the hamburger menu next to the FAQ and About anyway, if possible. But I donât know if discourse allows changing that.
This is because they donât use text for the logo branding. Itâs literally an image. Which is honestly fine, but if you use dynamic themes then it really should be a SVG instead of a PNG.
Agreed. But They use bootstrap so like I said earlier just change the class to container-fluid
will fix this âbugâ.
Probably, thatâs not a bootstrap style though from what I see
Use .container-fluid for a full width container, spanning the entire width of the viewport.
Nono I mean, the style that is applied to that link container isnât Bootstrap default
Also could be base64 since they already seem to optimise for âcriticalâ styles
I donât know enough about Ember to know how it mangled bootstrap.
If it supports Tree-Shaking then I suppose the minified CSS assets would remove the unused styles.