[Webkit-unassigned] [Bug 261137] New: text-box-trim leading radically different results from Figma

[bugzilla-daemon at webkit.org]

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

            Bug ID: 261137
           Summary: text-box-trim leading radically different results from
                    Figma
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Compositing
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mic.gallego at gmail.com
                CC: simon.fraser at apple.com

Created attachment 467549

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

comparison

Hi,

We are currently considering using text-box-trim as a progressive enhancement, to ensure the spacing looks consistent across a wide range of fonts.

Figma recently introduced support for text-box-trim/text-box-edge, unfortunately there is a big discrepancy between what Figma renders and what Safari TP renders. I have no idea which one is incorrect, but the Safari result is unfortunately unusable (so I hope Safari is wrong).

Figma internally uses "cap" for text-box-edge and "both" for text-box-trim. I think the choice to use cap instead of cap alphabetic is to ensure it works best even when all the text is in uppercase.

I have attached a screenshot of the differences. I also set a minimum test case that reproduce the odd alignment on Safari: https://codepen.io/bakura10/pen/jOXVNpj

-- 
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/20230905/dd475d0b/attachment.htm>