Responsive navbar not working properly #164

Closed
opened 2025-12-29 15:35:38 +01:00 by adam · 2 comments
Owner

Originally created by @bellwood on GitHub (Jul 7, 2016).

When the viewport is less than 1121 px wide but greater than 768 px wide the header menus stack instead of going responsive (hamburger)

You can replicate this issue with an iPad mini in portrait or landscape rotation

Originally created by @bellwood on GitHub (Jul 7, 2016). When the viewport is less than 1121 px wide but greater than 768 px wide the header menus stack instead of going responsive (hamburger) You can replicate this issue with an iPad mini in portrait or landscape rotation
adam added the type: bug label 2025-12-29 15:35:38 +01:00
adam closed this issue 2025-12-29 15:35:39 +01:00
Author
Owner

@bellwood commented on GitHub (Jul 7, 2016):

This also causes an issue where the padding on .body only accounts for the sticky header at its proper height... When the menus stack, the padding isnt enough and section content becomes hidden underneath the header

@bellwood commented on GitHub (Jul 7, 2016): This also causes an issue where the padding on .body only accounts for the sticky header at its proper height... When the menus stack, the padding isnt enough and section content becomes hidden underneath the header
Author
Owner

@bellwood commented on GitHub (Jul 9, 2016):

So right now the navbar collapses via the following LESS variable chain:

Point at which the navbar begins collapsing
@grid-float-breakpoint-max == (@grid-float-breakpoint - 1)

Point at which the navbar becomes uncollapsed
@grid-float-breakpoint == @screen-sm-min
@screen-sm-min == @screen-sm
@screen-sm == 768px

..and confirmed the navbar goes "hamburger" at ~768px.

With the current wording/spacing/etc we need the navbar to collapse at 1120px (+/- 1px)

Not sure if you are customizing bootstrap at all via custom LESS where in this could be changed but failing that we can use a custom media query to change the breakpoint.

I'll throw together a pull request and let you decide if that's the best route.

@bellwood commented on GitHub (Jul 9, 2016): So right now the navbar collapses via the following LESS variable chain: Point at which the navbar begins collapsing @grid-float-breakpoint-max == (@grid-float-breakpoint - 1) Point at which the navbar becomes uncollapsed @grid-float-breakpoint == @screen-sm-min @screen-sm-min == @screen-sm @screen-sm == 768px ..and confirmed the navbar goes "hamburger" at ~768px. With the current wording/spacing/etc we need the navbar to collapse at 1120px (+/- 1px) Not sure if you are customizing bootstrap at all via custom LESS where in this could be changed but failing that we can use a custom media query to change the breakpoint. I'll throw together a pull request and let you decide if that's the best route.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#164