Closed
Bug 668837
Opened 13 years ago
Closed 6 years ago
FlexBox moz-box-orient horizontal orientation is ingored in absolute positioning mode
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: leonbrag, Unassigned)
Details
(Whiteboard: DUPEME)
Attachments
(2 files)
User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; MS-RTC LM 8; InfoPath.3; .NET CLR 1.1.4322) Steps to reproduce: When flex box is used together with the absolute possitioning, horizontal box orientation is ignored Actual results: Instead of horizontal child element positioning, vertical positioning is used Expected results: Absolute positining should NOT break flex box orientation. The sample code attached here works in every browser (Chrome, Safari, IE10 Platform Preview), but not FF. To make code work in FF, you need to comment out position: absolute style. This is clearly a bug.
Updated•13 years ago
|
Attachment #543458 -
Attachment mime type: text/plain → text/html
Comment 1•13 years ago
|
||
Dupe of Bug 640443 (and thus dependent on Bug 455338)?
Component: General → Layout
Product: Firefox → Core
QA Contact: general → layout
Comment 2•13 years ago
|
||
No, actually not related to that at all.
It's just that making something absolutely positioned makes it a block, not a box. And then the whole box-orient thing doesn't apply, since it's not a box.
> This is clearly a bug.
Why clearly? Part of the definition of "display: -moz-box" (not to be confused with the proposed "display: flexbox", which is a completely different thing) is that it can only apply to non-absolutely-positioned elements, just like "display: inline".
Whiteboard: DUPEME
Comment 3•13 years ago
|
||
In particular, -moz-box is NOT an implementation of http://dev.w3.org/csswg/css3-flexbox/
Then it appears to be a documentation issue. This article seems to imply (in the paragraph "Okay, cool, but does it work in real life?") that -moz-box is an implementation of the http://www.w3.org/TR/css3-flexbox/ (in the first "The flexible box model" paragrah). Should above article be ammended to clearly state per "https://developer.mozilla.org/en/CSS/-moz-box-orient" that "Flexible Box Layout Module (W3C Working Draft) Note: The current state of this specification does not reflect Mozilla's or WebKit's implementation." to avoid any confusion. Thanks
Sorry, original article link did no make it: http://hacks.mozilla.org/2010/04/the-css-3-flexible-box-model/
Comment 6•13 years ago
|
||
Yeah, that article is just wrong on that point, sadly. Chris, Paul, could we get it fixed?
Comment 7•13 years ago
|
||
I'm taking care of it.
Comment 8•13 years ago
|
||
I've updated this paragraph, stating that Mozilla and Webkit have implemented *a* box model, and adding the notice suggested by LB.
Comment 9•12 years ago
|
||
And again, prepare a testcase then find a dup when filing the bug. From comment 2 I'll take this is the expected -moz-box behavior? I would really love to get rid of nested divs just to work around this in the B2G SMS app.
Comment 10•11 years ago
|
||
Seems to be fixed with the current spec.
Comment 11•10 years ago
|
||
Can this be related to bug 874718 ?
Comment 12•10 years ago
|
||
No. The "-moz-box" model & its properties are completely separate from the "new flexbox" properties. (as are their implementations), as noted in comment 3.
Comment 13•6 years ago
|
||
This is probably WONTFIX at this point, for reasons described in comment 2, and also since we're moving away from XUL/-moz-box so we're not really looking to add more features/functionality XUL & -moz-box.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•