[Webkit-unassigned] [Bug 232910] New: [LFC][GTK] LFC Integration doesn't work on GTK because GTK always selects the complex text path

[bugzilla-daemon at webkit.org]

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

            Bug ID: 232910
           Summary: [LFC][GTK] LFC Integration doesn't work on GTK because
                    GTK always selects the complex text path
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Canvas
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: agoldmints at igalia.com
                CC: dino at apple.com

When choosing whether to use the new LFC paths, there are a number of reason that LFC could be disabled, one of which is that the FontCascade uses the complex text path. On GTK, there is an override that results in the complex text path always being used for all text, which means that LFC is never used in LFC integration mode.

-- 
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/20211109/02349a3b/attachment.htm>