Bug 6135

Summary: WebKit should render ligatures
Product: WebKit Reporter: mitz
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Enhancement CC: ap, emacemac7, eric, hsivonen, ian, justin.garcia, karlcow, rik, sam
Priority: P3    
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
Attachments:
Description Flags
testcase for ligature
none
rendering in safari, firefox, chrome none

mitz
Reported 2005-12-18 10:15:45 PST
The CG code path in WebTextRenderer does not render automatic ligatures.
Attachments
testcase for ligature (407 bytes, text/html)
2022-12-26 19:44 PST, Karl Dubost 		no flags
Details
rendering in safari, firefox, chrome (133.68 KB, image/png)
2022-12-26 19:46 PST, Karl Dubost 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Timothy Hatcher
Comment 1 2008-10-17 09:26:27 PDT
We should consider using ligatures in text runs that are greater than some large font size. So headlines and things look good. That might be acceptable performance wise.
mitz
Comment 2 2008-10-17 09:31:43 PDT
Setting a font size threshold may be problematic for things that smoothly animate size.
Karl Dubost
Comment 3 2022-12-26 19:44:00 PST
Created attachment 464218 [details] testcase for ligature This is probably solved.
Karl Dubost
Comment 4 2022-12-26 19:46:17 PST
Created attachment 464219 [details] rendering in safari, firefox, chrome The rendering in Firefox and Safari is working The one in Chrome not so much.
mitz
Comment 5 2022-12-26 19:53:05 PST
Bug 99113 addressed the "CG code path" part of this, and bug 100188 enabled ligatures by default. *** This bug has been marked as a duplicate of bug 100188 ***
Note You need to log in before you can comment on or make changes to this bug.