Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

125% magnification breaks front-page styling #1014

Closed
carnesen opened this Issue Aug 20, 2015 · 2 comments

Comments

Projects
None yet
3 participants
Contributor

carnesen commented Aug 20, 2015

The front page of bitcoin.org shows as the authors intended at "normal" magnification (100%) and also at 110%. But for some reason in going from 110% to 125% the content width increases dramatically (far more than the extra 15% would imply) and also the list "Fast peer-to-peer transactions ... Worldwide payments" goes vertical. Screen shot attached.
screen shot 2015-08-20 at 09 38 58

Contributor

harding commented Aug 20, 2015

On Firefox 31.8 with a 1440px window, scaling steps appear to be proportional. What @carnesen seems to be observing is the switch from the desktop layout to the mobile layout that occurs when the div.body box overflows the html body box. I'm not sure this is an actual bug, but I'll tag it as such until @saivann has a chance to investigate.

@harding harding added the Bug label Aug 20, 2015

saivann added a commit to saivann/bitcoin.org that referenced this issue Aug 20, 2015

Contributor

saivann commented Aug 20, 2015

@carnesen I have opened pull request #1016 to fix one of the issues your seeing with the icons being suddenly left-aligned and not inline-displayed, please feel free to try the live preview and comment there. Otherwise what you are describing seems to be the intended behavior (switching to the mobile layout). Please leave a comment if you can think of any usability issue this can cause.

I am not aware of any way to allow desktop browsers to zoom on the desktop layout without triggering the mobile layout as it reduces the available width on the screen, and that is how mobile layouts enter into play thanks to @media CSS rules.

@carnesen carnesen closed this Aug 20, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment