Bug 232910 - [LFC][GTK] LFC Integration doesn't work on GTK because GTK always selects the complex text path
Summary: [LFC][GTK] LFC Integration doesn't work on GTK because GTK always selects the...
Status: RESOLVED DUPLICATE of bug 235266
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-09 15:25 PST by Arcady Goldmints-Orlov
Modified: 2022-01-17 09:53 PST (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arcady Goldmints-Orlov 2021-11-09 15:25:27 PST 
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.
Comment 1 Arcady Goldmints-Orlov 2022-01-17 09:53:25 PST 
This has been fixed by r288070 allowing LFC integration to work with the complex text path.

*** This bug has been marked as a duplicate of bug 235266 ***