-
Notifications
You must be signed in to change notification settings - Fork 1.4k
About-menu shows vertical scrollbar with 5 or more contact link items #14
Comments
Visible when there are 5 or more items on the about-menu. Fixes fixes mmistakes#14
@teelahti I'm still playing around with the menu to get it just right on all devices. On tablets in landscape orientation and other small devices, when the menu was too tall it fell outside of the viewport, and since the menu is fixed position it was impossible to get at those links. Trying to make it so the scrollbar triggers only when the menu falls outside of view. Check the animated gif below to see what I'm trying to avoid. |
True, that is not desirable either. What if you position avatar image and name+description side by side on tablet resolutions? That would still leave mobile devices broken, though. |
I think I have it worked out I just haven't had time to update the .less On Mon, Mar 3, 2014 at 3:46 PM, Tero Teelahti [email protected]:
|
bump... since I'm working on this right now. Problem is the scrollbar won't scroll to the later elements. I'm not sure what's limiting the height or preventing the overflow. The scrollbar does appear and scroll a tiny bit though. |
@djechlin The real problem with the nav is the fixed positioning and people trying to make the menu deeper than it was originally intended to be. If you want to solve the problem the easy way and don't care about the nav being in view all the time, you can change Then you can remove the Otherwise you can play around with the If you want to get fancy you can use media queries that filter on height in addition to width to cover your bases. |
When there are 4 or less items in the about-menu it works flawlessly. If there are 5 or more, it shows a vertical scrollbar. This scrollbar was not visible on January 15th of 2014 version; one of the commits since then has changed the menu height. Reason for the current behavior is at main.css
Tested and reproducible with Chrome 35, IE 11, and FF 28.
The text was updated successfully, but these errors were encountered: