Bug 108133

Summary: SVG fonts don't compute widths properly when going through the complex text path
Product: WebKit Reporter: Tony Chang <tony>
Component: SVGAssignee: Stephen Chenney <schenney>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: bfulgham, fmalita, pdr, schenney, zimmermann
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 109833    
Bug Blocks:    
Attachments:
Description Flags
test case
none
DRT Test Case (also crashes in browser) none

Tony Chang
Reported 2013-01-28 16:41:08 PST
Created attachment 185100 [details] test case I'll upload a test case. Notice that when selecting text in the test case, the selection gets off. I think this is a bug with SVG fonts, but I'm not sure.
Attachments
test case (3.62 KB, text/html)
2013-01-28 16:41 PST, Tony Chang 		no flags
Details
DRT Test Case (also crashes in browser) (837 bytes, text/html)
2013-02-13 13:06 PST, Stephen Chenney 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Philip Rogers
Comment 1 2013-01-28 16:51:35 PST
This appears to only occur with the combination of complex text, SVG fonts, and the CSS property text-rendering: optimizelegibility. CC'ing our font expert.
Stephen Chenney
Comment 2 2013-01-29 06:24:52 PST
Is this bug related to Chromium https://code.google.com/p/chromium/issues/detail?id=170423?
Tony Chang
Comment 3 2013-01-29 11:58:30 PST
(In reply to comment #2) > Is this bug related to Chromium https://code.google.com/p/chromium/issues/detail?id=170423? Yes, on Chromium Linux we crash, but I think if we fix this, it will also fix the crash.
Stephen Chenney
Comment 4 2013-02-13 13:06:36 PST
Created attachment 188158 [details] DRT Test Case (also crashes in browser) Hitting the real issue in debug builds requires removing a ASSERT_NOT_REACHED that should not be present at line 209 of SimpleFontData.h.
Brent Fulgham
Comment 5 2022-07-15 15:59:44 PDT
Safari, Chrome, and Firefox all agree on rendering for this test case. I don't believe there is any remaining compatibility issue.
Note You need to log in before you can comment on or make changes to this bug.