From a9c829bc0c75dd7723e6c74e1defaab5dbb4c00b Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Sat, 28 Dec 2013 22:47:03 -0800 Subject: Rearrange repository contents because muahahahahahaha --- docs/examples/non-responsive/index.html | 105 ++++++++++++++++++++++++++++++++ 1 file changed, 105 insertions(+) create mode 100644 docs/examples/non-responsive/index.html (limited to 'docs/examples/non-responsive/index.html') diff --git a/docs/examples/non-responsive/index.html b/docs/examples/non-responsive/index.html new file mode 100644 index 000000000..bbed7efb9 --- /dev/null +++ b/docs/examples/non-responsive/index.html @@ -0,0 +1,105 @@ + + + + + + + + + + + + + Non-responsive Template for Bootstrap + + + + + + + + + + + + + + + + + + + +
+ + + +

What changes

+

Note the lack of the <meta name="viewport" content="width=device-width, initial-scale=1.0">, which disables the zooming aspect of sites in mobile devices. In addition, we reset our container's width and are basically good to go.

+ +

Regarding navbars

+

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.

+ +

Browsers, scrolling, and fixed elements

+

Non-responsive layouts highlight a key drawback to fixed elements. Any fixed component, such as a fixed navbar, will not be scrollable when the viewport becomes narrower than the page content. In other words, given the non-responsive container width of 970px and a viewport of 800px, you'll potentially hide 170px of content.

+

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.

+ +

Non-responsive grid system

+
+
One third
+
One third
+
One third
+
+ +
+ + + + + + + + -- cgit v1.2.3