aboutsummaryrefslogtreecommitdiff
path: root/examples
diff options
context:
space:
mode:
authorMark Otto <[email protected]>2013-12-15 22:09:45 -0800
committerMark Otto <[email protected]>2013-12-15 22:09:45 -0800
commitca14b9652cb1d1adb2561fac37db0bb75c3b5838 (patch)
tree2fc7c0f08349896687c5275c85cbd5cf6d0ee263 /examples
parent4ee93c9f8529cfeef56d4178b91e1ddcb0bff09c (diff)
downloadbootstrap-ca14b9652cb1d1adb2561fac37db0bb75c3b5838.tar.xz
bootstrap-ca14b9652cb1d1adb2561fac37db0bb75c3b5838.zip
inform the people that fixed positioning ain't all it's cracked up to be /cc #11888
Diffstat (limited to 'examples')
-rw-r--r--examples/non-responsive/index.html4
1 files changed, 4 insertions, 0 deletions
diff --git a/examples/non-responsive/index.html b/examples/non-responsive/index.html
index 1c56b300f..73baa43e5 100644
--- a/examples/non-responsive/index.html
+++ b/examples/non-responsive/index.html
@@ -82,6 +82,10 @@
<h3>Regarding navbars</h3>
<p>As a heads up, the navbar component is rather tricky here in that the styles for displaying it are rather specific and detailed. Overrides to ensure desktop styles display are not as performant or sleek as one would like. Just be aware there may be potential gotchas as you build on top of this example when using the navbar.</p>
+ <h3>Browsers, scrolling, and fixed elements</h3>
+ <p>Non-responsive layouts highlight a key drawback to fixed elements. <strong class="text-danger">Any fixed component, such as a fixed navbar, will not be scrollable when the viewport becomes narrower than the page content.</strong> In other words, given the non-responsive container width of 970px and a viewport of 800px, you'll potentially hide 170px of content.</p>
+ <p>There is no way around this as it's default browser behavior. The only solution is a responsive layout or using a non-fixed element.</p>
+
<h3>Non-responsive grid system</h3>
<div class="row">
<div class="col-xs-4">One third</div>