Intent to Implement and Ship: CSS Flexbox: New behavior for absolute-positioned children

129 views
Skip to first unread message

Christian Biesinger

unread,
Aug 5, 2015, 7:56:37 PM8/5/15
to blink-dev
cbies...@chromium.org https://drafts.csswg.org/css-flexbox/#abspos-items A previous version of the Flexbox spec set the static position of abspos children as if they were a 0x0 flex item. However, the latest version of the spec takes them fully out of flow and sets the static position based on align and justify properties.
A note on interactions with the css-align spec (I previously misunderstood how this worked):
The flexbox spec (what I am implementing) is only about calculating the *static* position of an abspos child, whereas the css-align spec only affects the positioning of an abspos item within its containing block if the position is *not* static. So the two specs cover different situations and do not conflict. I am not currently intending to implement the latter part.
The new behavior is much more intuitive and useful than the old behavior -- assuming a 0x0 size will not lead to a reasonable outcome in many cases.

Firefox: Public support Edge: Shipped Safari: No public signals Web developers: No signals
Small -- IE already shipped this, Firefox wants to ship it. This only makes a visible difference if there is an abspos item in a flexbox *and* it does not have a position specified *and* the justify/align properties are not the default.
No
Yes No OWP bug, regular bug: https://code.google.com/p/chromium/issues/detail?id=517265 https://www.chromestatus.com/features/6600926009753600

Rick Byers

unread,
Aug 5, 2015, 9:59:16 PM8/5/15
to Christian Biesinger, blink-dev
Sounds very low risk to me - LGTM

On Wed, Aug 5, 2015 at 7:56 PM, Christian Biesinger <cbies...@chromium.org> wrote:
cbies...@chromium.org https://drafts.csswg.org/css-flexbox/#abspos-items A previous version of the Flexbox spec set the static position of abspos children as if they were a 0x0 flex item. However, the latest version of the spec takes them fully out of flow and sets the static position based on align and justify properties.
A note on interactions with the css-align spec (I previously misunderstood how this worked):
The flexbox spec (what I am implementing) is only about calculating the *static* position of an abspos child, whereas the css-align spec only affects the positioning of an abspos item within its containing block if the position is *not* static. So the two specs cover different situations and do not conflict. I am not currently intending to implement the latter part.
The new behavior is much more intuitive and useful than the old behavior -- assuming a 0x0 size will not lead to a reasonable outcome in many cases.

Firefox: Public support

TAMURA, Kent

unread,
Aug 7, 2015, 3:37:57 AM8/7/15
to Rick Byers, Christian Biesinger, blink-dev
LGTM2

--
TAMURA Kent
Software Engineer, Google


Jochen Eisinger

unread,
Aug 7, 2015, 3:39:13 AM8/7/15
to TAMURA, Kent, Rick Byers, Christian Biesinger, blink-dev
LGTM3
Reply all
Reply to author
Forward
0 new messages