[Webkit-unassigned] [Bug 244762] New: Redesign the interaction between primary font selection and unicode-range

[bugzilla-daemon at webkit.org]

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

            Bug ID: 244762
           Summary: Redesign the interaction between primary font
                    selection and unicode-range
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Text
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mmaxfield at apple.com
                CC: mmaxfield at apple.com

For content like this:

```
@font-face {
    font-family: a;
    src: url("MyFont.ttf");
    unicode-range: some range;
}
@font-face {
    font-family: a;
    src: url("MyOtherFont.ttf");
    unicode-range: a distinct range that doesn't intersect the other font's range;
}
```

It's non-obvious which font should be considered the primary font for the purpose of inline layout (vertical height calculations). Right now we pick MyOtherFont.ttf just because it's last in content order, but that's wasteful because it's totally possible that none of the characters will actually be rendered with that font.

We should try to redesign this in a way that:
a) makes more intuitive sense
b) is consistent with other browsers
c) matches the spec (potentially by modifying the spec to match whatever this redesign yields)

-- 
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/20220903/eaf0bde3/attachment.htm>