Note that there are some explanatory texts on larger screens.

plurals
  1. POFluid or fixed grid system, in responsive design, based on Twitter Bootstrap
    primarykey
    data
    text
    <p>I'm getting confused about the various options in the <a href="http://twitter.github.com/bootstrap/scaffolding.html%5C" rel="noreferrer">twitter bootstrap grid</a>, and how they go together. </p> <p>To begin with, you can have an ordinary fixed <code>container</code>, or a <code>container-fluid</code>. </p> <p>Then either one can include either an ordinary <code>row</code>, or a fluid row, <code>row-fluid</code>. That is, you can have a fixed container with a fluid row, or a container-fluid... with a fixed row?</p> <p>Then on top of that, you can include the 'responsive' media queries, or not. </p> <p>I am getting confused as to how these things interact. But let's start with one obvious example. </p> <p>On <a href="http://twitter.github.com/bootstrap/scaffolding.html" rel="noreferrer">the examples page</a> itself, there's what's presented as an example of both a <a href="http://twitter.github.com/bootstrap/scaffolding.html#gridSystem" rel="noreferrer">fixed grid</a> and a <a href="http://twitter.github.com/bootstrap/scaffolding.html#fluidGridSystem" rel="noreferrer">fluid grid</a></p> <p>However, in my browser, on that example page itself -- both grids behave identically. Perhaps because the example page uses the optional responsive media queries? In <strong>both</strong> grid examples, if I start gradually narrowing my browser window, the grid elements do <em>not</em> get gradually narrower -- once a certain (responsive) boundary width is reached, they snap to a smaller size, and again at further boundary widths. But both the ordinary 'fixed' example AND the 'fluid' example behave exactly the same here -- so what the heck is the difference?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload