[Webkit-unassigned] [Bug 165062] New: [css-flex] Flex container baseline wrongly uses content-box bottom to synthesize baselines

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=165062

            Bug ID: 165062
           Summary: [css-flex] Flex container baseline wrongly uses
                    content-box bottom to synthesize baselines
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jfernandez at igalia.com
                CC: simon.fraser at apple.com

Created attachment 295409
  --> https://bugs.webkit.org/attachment.cgi?id=295409&action=review
Test case to reproduce the issue.

According the the last draft version of the Flexible Box specification:

https://drafts.csswg.org/css-flexbox/#flex-baselines
"if the flex container has at least one flex item, the flex container’s first/last main-axis baseline set is generated from the alignment baseline of the first/last flex item. (If that item has no alignment baseline parallel to the flex container’s main axis, then one is first synthesized from its border edges.)"

The CSS WG has agreed as well that we should do the same for orthogonal flex items:

https://github.com/w3c/csswg-drafts/issues/373
https://lists.w3.org/Archives/Public/www-style/2016Sep/0000.html

Also, while I couldn't find it in the specs, the CSS WG has agreed that an empty Flexbox containers should synthesize its baseline using its border-box bottom edge:

https://github.com/w3c/csswg-drafts/issues/439

The attached test cases prove that current implementation doesn't follow the spec.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161124/8522e665/attachment-0001.html>