Closed
Bug 1110161
Opened 11 years ago
Closed 11 years ago
Flex items with position: absolute shouldn't participate in flex layout
Categories
(Core :: Layout, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 874718
People
(Reporter: bogdan.gribincea, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2236.0 Safari/537.36
Steps to reproduce:
Inside a container with display: flex and several children, set one child (or several) to position: absolute.
Actual results:
The element is correctly positioned and sized as per the top/left width/height properties if present. They don't affect the outcome.
However, it's presence inside the flex container affects the layout of the other flex items.
Expected results:
The flex layout should look like that element didn't exist.
Quote from the spec http://dev.w3.org/csswg/css-flexbox/#abspos-items (Editor’s Draft, 19 November 2014):
"An absolutely-positioned child of a flex container does not participate in flex layout. However, it does participate in the reordering step (see order), which has an effect in their painting order."
|
Reporter | |
Updated•11 years ago
|
Component: Untriaged → Layout
Product: Firefox → Core
|
|
||
Comment 1•11 years ago
|
||
Yes, this is a spec change that we haven't updated to yet.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
|
||
Comment 2•9 years ago
|
||
Looks like we didn't have a concrete testcase here, but in any case, this should be fixed in latest Firefox Nightly builds (version 52) from https://nightly.mozilla.org/
Marking VERIFIED as a dupe of the bug that covers the spec text quoted in comment 0 here.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•