Comments for CSS 3: Progress! (Updated)
.hbox, .vbox { -webkit-box-flex: attr(flex, number); }
...
The proposed spec for attr does not yet cover keywords. Keywords are needed for box-pack, box-orient, box-align, box-direction and box-lines.
"CSS is not supposed to be used for that" is what has kept CSS from crawling out of the primordial pit for nearly a decade. It's really too bad that our expectations have been lowered so far.
That said, if there's some other part of the web stack that you think should take this one natively (and no, JavaScript doesn't count), then I guess I'm all ears.
Regards
Anyway, this is the first I've heard about flexboxes and I'm excited to see it added to CSS3.
Hmm. Hopefully, it can it be used to do this without the result being jumbled when publisher CSS isn't applied…
Some kind of solution is sorely needed, layout is the major pain point of Ajax right now.
[1] http://2ality.blogspot.com/2009/07/css-layout-soon-good-enough-for-guis.html
Thanks for this article. I was just trying this on a chrome extension and wasn't able to nest boxes and flex some of them. The problem was that display:block for box children was overiding display: -webkit-box. I added !important to the latter and now it works.
Hope this helps ;)
Marcos
As Benjamin H-L hints, this makes me nervous about what this form "looks like" without the CSS -- for example, in a screen reader. Some of us remember how with css-based layouts we could finally have control over source order; this form is a step backward in that department.
Maybe an out-of-order form isn't the best example for using vboxes?