[Webkit-unassigned] [Bug 256937] New: [css-flexbox][baseline-alignment] Flex item's with different writing mode from flex container should not always synthesize a baseline

[bugzilla-daemon at webkit.org]

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

            Bug ID: 256937
           Summary: [css-flexbox][baseline-alignment] Flex item's with
                    different writing mode from flex container should not
                    always synthesize a baseline
           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: sgill26 at apple.com
                CC: bfulgham at webkit.org, simon.fraser at apple.com,
                    zalan at apple.com

Created attachment 466390

  --> https://bugs.webkit.org/attachment.cgi?id=466390&action=review

Testcase

Flex layout will call into a flex item's firstLineBaseline/lastLineBaseline in order to compute an ascent for the item to use in baseline alignment. If the flex item has a different writing mode from the flex container then it will return std::nullopt because of the check for isWritingModeRoot() and as a result will have a baseline synthesized. In the attached test case (reduced from css-flexbox/alignment/flex-align-baseline-001.html) we should still be able to compute baseline values for the flex items since the block axis for the items is parallel to the alignment context.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230518/56c86392/attachment.htm>