Ensure that placeholders don't interfere with flex items establishing container's baseline

RESOLVED FIXED

Status

()

Core
Layout
RESOLVED FIXED
3 years ago
a year ago

People

(Reporter: dholbert, Unassigned)

Tracking

Trunk
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
(spinning off from bug 1054058 comment 5)

STR:
 1. Load attached testcase, with an abspos flex item followed by a normal flex item.

EXPECTED RESULTS:
"Text Outside" and "Text Inside" should be baseline-aligned.

ACTUAL RESULTS:
"Text Outside" is aligned with the bottom of the flex-container's content-box. (i.e. the flex container's baseline is at the bottom of its content-box.)


As described in bug 1054058 comment 6, our "ACTUAL RESULTS" are actually "correct" for the abspos flex-container-child behavior that we currently implement (from an earlier version of the flexbox spec, mentioned/linked in bug 874718 comment 5).  Basically, right now we wrap the placeholder in an anonymous flex item, and that anonymous flex item is free to responsible for establishing the flex container's baseline. (and since it's empty, we end up falling back to just using the container's content-box bottom, per the final "otherwise" at http://dev.w3.org/csswg/css-flexbox-1/#flex-baselines)

But the spec doesn't say that placeholders should get wrapped in anonymous flex items anymore -- so once we implement the new spec behavior (in bug 874718), we should make sure the abspos element in the attached testcase doesn't interfere with its sibling establishing the container's baseline.
(Reporter)

Comment 1

3 years ago
Created attachment 8553221 [details]
testcase 1
(Reporter)

Comment 2

a year ago
I get EXPECTED RESULTS in latest trunk. Resolving as FIXED by bug 874718.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.