You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think some of the media queries in docs.css really be ought to be standard in every project, ie moved to the core. Specific examples.
Snippet 1
@media (min-width:940px) {
.nav-collapse.collapse {
height: auto !important;
}
}
Took me a while to figure out what was going on here. I collapsed the nav while in <940px (ie while the collapse toggle is visible), then extended the width and found the entire nav disappeared altogether! That's because .collapse has overflow: hidden set when collapsed, hence need height: auto as in the docs.
Snippet 2
@media (max-width:768px) {
body {
padding-top:0;
}
}
Without this, I had a gap between the top of the page and the navbar (at <768px resolution), as I had a padding-top set for body (as in the nav).
Snippet 3?
This possibly applies to other media queries in the docs, particularly subnav-related. I haven't used subnav, so not sure.
The text was updated successfully, but these errors were encountered:
I think some of the media queries in docs.css really be ought to be standard in every project, ie moved to the core. Specific examples.
Snippet 1
Took me a while to figure out what was going on here. I collapsed the nav while in <940px (ie while the collapse toggle is visible), then extended the width and found the entire nav disappeared altogether! That's because .collapse has overflow: hidden set when collapsed, hence need height: auto as in the docs.
Snippet 2
Without this, I had a gap between the top of the page and the navbar (at <768px resolution), as I had a padding-top set for body (as in the nav).
Snippet 3?
This possibly applies to other media queries in the docs, particularly subnav-related. I haven't used subnav, so not sure.
The text was updated successfully, but these errors were encountered: