Site logo and icons do not play together well on small screen.
Expected:
- either scale logo or use the smaller one
Screenshot from Android:
Workaround:
Thanks!
Site logo and icons do not play together well on small screen.
Expected:
Screenshot from Android:
Workaround:
Thanks!
Is this Mobile view or a narrowed Desktop view only?
If Desktop, is it “normal use” to have the viewport so narrow?
Oh so true. On mobile there is no problem and on the desktop you should never have the window that narrow. But thats just for me, I dont now if @gtanczyk uses narrow windows…
Screenshot was done on desktop, however it’s the same on mobile browser, when your logo width exceeds some threshold.
Please also mind I18n translations for Log in, Sign in buttons. In polish language it is “Logowanie” and “Rejestracja”, which takes few more pixels than corresponding english words.
This is not a bug report, the layout is different in mobile. Please provide mobile screenshots, a tiny desktop / laptop / tablet width makes no sense.
Hello, I have uploaded screenshot from mobile.
In the case of long translated words, if in your language “login” is “mshehjensgsybsnjjebeggsjksoeomendmxkskelflr” you will need to set a max-width via CSS on the relevant controls, or make the mobile logo width smaller via CSS.
Thanks for providing workaround.
More specifically, now that I am not on an iPad but in front of a real computer, these CSS rules already exist, so you can amend them or add to them in Admin, Customize, CSS/HTML:
.d-header button.login-button {
margin-left: 7px;
max-width: 75px;
white-space: nowrap;
}
here we set a max width on login-button
and indicate the text should not wrap to the next line.
.d-header #site-logo {
max-width: 125px;
}
there is already a max-width specified for the mobile logo CSS, so you can make it smaller as needed with a CSS override.
How about using display: table
and display: table-cell
along with white-space: nowrap
? I am also thinking about text-overflow: ellipsis
and max-width
on “Log in” button.
Perhaps this way there will be no need for CSS overrides. I will test it today and maybe start a PR.
Be careful, changes to header can be very dangerous, as we have seen from our (1st and 2nd failed) attempts to use flexbox in the header…