Thanks. Exactly the kind of explanation I needed.
On Monday, December 3, 2012 3:28:28 PM UTC-6, Renoir Boulanger wrote: > > This is not a Twitter bootstrap question. But more a HTML semantics > question. > > Tables are made to show tabular data. If you have titles, sections, and > values. A table is perfect. > > In opposition; if you only have a few titles, and title: value format, a > Definition list would be perfect. > > <section> > <h2>User details</h2> > <dl><dt>Full name</dt><dd>Renoir Boulanger</dd></dl> > </section> > > > Regarding bootstrap and responsiveness. > > But there, again, it is not bootstrap specific. I think they have what I > am mentionning, but I am late on versions! (I'm still using 1.4). > > I know that Zurb Foundation has this. But really, it is only a matter of > creating a class in the proper media query. > > Answer: > > In a table with per-row action drop down; I recommend you make each column > per value/button and you can add a class name on each td and th > representing columns you may not want visible. > > Then, when the browser gets to a size the media query containing that > class gets activated; the class will apply. And hide the superfluous > columns who has that class (e.g. hide-mq-lt-1024) > > Now that you know this (if you didn't yet) is that you may want to > minimize resource loading if you already know you are on a small screen. > > That's an other topic again :) > > Hope it helped > >
