Bug 65795

Summary: [CG] SVG path drawn incorrectly when some endpoints are offscreen
Product: WebKit Reporter: Tim Horton <thorton>
Component: SVGAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: krit, rwlbuis, zimmermann
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
repro
none
correct screenshot
none
incorrect screenshot none

Tim Horton
Reported 2011-08-05 16:00:10 PDT
Steps to Reproduce: 1. Open attached file. 2. Slowly reduce the size of the browser window (slowly!) 3. Note that when the browser window becomes slightly smaller than the image, the path is drawn incorrectly (the curved regions are filled in!). <rdar://problem/8185406>
Attachments
repro (989 bytes, image/svg+xml)
2011-08-05 16:00 PDT, Tim Horton 		no flags
Details
correct screenshot (30.80 KB, image/png)
2011-08-05 16:01 PDT, Tim Horton 		no flags
Details
incorrect screenshot (28.33 KB, image/png)
2011-08-05 16:01 PDT, Tim Horton 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Tim Horton
Comment 1 2011-08-05 16:00:34 PDT
Created attachment 103125 [details] repro
Tim Horton
Comment 2 2011-08-05 16:01:26 PDT
Created attachment 103126 [details] correct screenshot
Tim Horton
Comment 3 2011-08-05 16:01:38 PDT
Created attachment 103127 [details] incorrect screenshot
Dirk Schulze
Comment 4 2011-08-05 23:25:11 PDT
Can you reduce the test case more? Is this CG specific or are other graphic libs affected as well?
Rob Buis
Comment 5 2012-04-30 14:41:48 PDT
This does not seem to happen on QtWebKit or chromium. CG only? Or already fixed?
Tim Horton
Comment 6 2012-04-30 14:44:47 PDT
Probably CG only. Also probably much harder to reproduce with the SVGImageCache.
Rob Buis
Comment 7 2012-04-30 14:45:30 PDT
This seems either gone, hard to reproduce or CG specific, going for CG specific for now.
Dirk Schulze
Comment 8 2014-05-12 06:37:51 PDT
I was VERY slow and could not reproduce it. Probably gone.
Note You need to log in before you can comment on or make changes to this bug.