Bug 45619

Summary: REGRESSION: Rendering of border-radius of borders with transparency broken in the nightlies
Product: WebKit Reporter: Marc Hoyois <marc.hoyois>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, bdakin, simon.fraser
Priority: P1 Keywords: InRadar, Regression
Version: 528+ (Nightly build)   
Hardware: Mac (Intel)   
OS: OS X 10.6   
Attachments:
Description Flags
HTML file showing the rendering problem
none
Screenshot of Safari 5.0.2's correct rendering
none
Screenshot of incorrect rendering in the latest Webkit none

Marc Hoyois
Reported 2010-09-12 12:42:25 PDT
Created attachment 67341 [details] HTML file showing the rendering problem Overview: If a div has nonzero border radius and nonopaque border color, darker strokes appear in the corners. Steps to reproduce: Simply open the attached HTML file in Webkit r67077 and then in Safari 5.0.2 and observe the difference. Expected result: See attached file 'Screenshot Safari 5.0.2.png' Actual result: See attached file 'Screenshot Webkit r67077.png' Platform: Tested on OS X 10.6.4 in Webkit 6533.18.5, r67077. Notes: The same problem appeared in some earlier versions of the nightlies, but I don't have numbers. The problem does not appear in Safari 5, Safari 5.0.1, and Safari 5.0.2
Attachments
HTML file showing the rendering problem (323 bytes, text/html)
2010-09-12 12:42 PDT, Marc Hoyois
no flags
Screenshot of Safari 5.0.2's correct rendering (11.21 KB, image/png)
2010-09-12 12:43 PDT, Marc Hoyois
no flags
Screenshot of incorrect rendering in the latest Webkit (11.17 KB, image/png)
2010-09-12 12:44 PDT, Marc Hoyois
no flags
Marc Hoyois
Comment 1 2010-09-12 12:43:30 PDT
Created attachment 67342 [details] Screenshot of Safari 5.0.2's correct rendering
Marc Hoyois
Comment 2 2010-09-12 12:44:02 PDT
Created attachment 67343 [details] Screenshot of incorrect rendering in the latest Webkit
Alexey Proskuryakov
Comment 3 2011-01-19 17:41:40 PST
Marc Hoyois
Comment 4 2011-04-20 14:06:12 PDT
This is fixed in r84360!
Alexey Proskuryakov
Comment 5 2011-04-20 16:28:49 PDT
Note You need to log in before you can comment on or make changes to this bug.