Closed
Bug 1264147
Opened 8 years ago
Closed 8 years ago
[css-flexbox] the 'order' property should affect absolutely-positioned flex children
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox48 | --- | affected |
People
(Reporter: MatsPalmgren_bugz, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
335 bytes,
text/html
|
Details |
https://drafts.csswg.org/css-flexbox/#abspos-items "... it does participate in the reordering step (see order), which has an effect on painting order." Background discussion: https://lists.w3.org/Archives/Public/www-style/2016Apr/0221.html
Reporter | ||
Comment 1•8 years ago
|
||
Fwiw, it works fine in Grid so feel free to copy the abs.pos. painting code from there.
Comment 2•8 years ago
|
||
The spec editors are currently proposing the removal of this spec-text: https://www.w3.org/mid/570C2819.1080406@inkedblade.net As I said in my response, though, I don't have strong feelings on how this should work (aside that it should be consistent between flex & grid).
Comment 3•8 years ago
|
||
(We don't explicitly exclude abspos children from "order" right now -- the reason it *looks* like we do is that we wrap abspos children's placeholders in anonymous flex items right now. So, those placeholders don't end up being directly children of the flex containers right now. That'll change soon, though, in 874718, which I'm hoping to fix in the next month or so.)
Reporter | ||
Comment 4•8 years ago
|
||
dbaron says the CSSWG has decided to change the Grid spec instead (bug 1266131).
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•