Bug 232910

Summary:	[LFC][GTK] LFC Integration doesn't work on GTK because GTK always selects the complex text path
Product:	WebKit	Reporter:	Arcady Goldmints-Orlov <crzwdjk>
Component:	Layout and Rendering	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED DUPLICATE
Severity:	Normal	CC:	aperez, bfulgham, dino, mrobinson, simon.fraser, zalan
Priority:	P2
Version:	WebKit Nightly Build
Hardware:	PC
OS:	Linux

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 ***