Closed Bug 562073 Opened 11 years ago Closed 8 years ago
implement box-lines property from css3-flexbox
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.3a5pre) Gecko/20100426 Minefield/3.7a5pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.3a5pre) Gecko/20100426 Minefield/3.7a5pre hi http://www.w3.org/TR/css3-flexbox/#propdef-box-lines parity webkit (-webkit-box-lines) Reproducible: Always
We're probably going to want to reimplement flexbox as it gets standardized; I don't see this happening before we do that.
Summary: implement box-lines for flexbox → implement box-lines property from css3-flexbox
The testcase uses an imaginary experimental property -moz-box-lines. I realize Bugzilla is not the place to evangelize. However seeing that things like rounded corners and shadows, though also experimental, are widely implemented I think it's fair to say that "CSS3 Flexboxes" have not gotten the attention it warrants, even though its significance can hardly be overstated. That is, if you're a web developer who's has had to put up with the madness of hacking up layouts with floats and absolute positioning! In order to build non-super-trivial layouts sanely, quickly and easily flexboxes are the way to go! Box-lines: multiple is the missing piece, because it's absence breaks usability (think small screens). Flexie a JS polyfill that makes flexboxes usable across browsers today, which for me presents nothing less than a revolution in the way I code web layouts. As a frontend web dev I'll argue that Flexboxes are the most important module of CSS3! Thanks, and I hope you'll excuse may non-implementation oriented comment...
This bug is invalid with the new css3-flexbox draft.
The new draft has "flex-wrap: wrap", which corresponds to the old "box-lines: multiple". Firefox 18 with layout.css.flexbox.enabled set doesn't seem to recognize the "-moz-flex-wrap" property at all.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 702508
You need to log in before you can comment on or make changes to this bug.