RESOLVED DUPLICATE of bug 21819 34656
Rounded Corner blowout 
https://bugs.webkit.org/show_bug.cgi?id=34656
Summary Rounded Corner blowout
Farina
Reported 2010-02-05 11:53:38 PST
Created attachment 48246 [details] This is a zoomed in version...I have the regular view, but this thing won't let me submit two images. As you can see from the attached images, CSS rounded corners don't render properly when a background and border are in place. In the images you will see what happens when I have a DIV with the following style: {height: 24px; padding: 5px; background: #000; border: 1px solid #EEE; color: #fff;}. Notice the WebKit version has much darker corners than the Gecko version. This is most noticeable when you have a border with a lighter color than the object's background color. Here are the two URLS since it will only let me submit one image: http://farina.me/Web/webkitLeakSmall.jpg http://farina.me/Web/webkitLeakBig.jpg
Attachments
This is a zoomed in version...I have the regular view, but this thing won't let me submit two images. (59.46 KB, image/jpeg)
2010-02-05 11:53 PST, Farina 		no flags
Details
Black Background Light Gray Border Border Bleeding Test Case (50 bytes, text/plain)
2010-06-02 13:05 PDT, Lauren Bosak 		no flags
Details
Complex CSS Gradient with Border Radius (no border) Test Case (49 bytes, text/plain)
2010-06-02 13:06 PDT, Lauren Bosak 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Lauren Bosak
Comment 1 2010-06-02 13:05:07 PDT
Created attachment 57685 [details] Black Background Light Gray Border Border Bleeding Test Case Added a test case.
Lauren Bosak
Comment 2 2010-06-02 13:06:40 PDT
Created attachment 57686 [details] Complex CSS Gradient with Border Radius (no border) Test Case Added a second similar test case.
Lauren Bosak
Comment 3 2010-06-02 13:08:42 PDT
I'm able to replicate on the current Safari nightly 531.22.7, Mac OS X 10.6.3.
Dimitri Glazkov (Google)
Comment 4 2010-06-04 19:58:18 PDT
*** This bug has been marked as a duplicate of bug 21819 ***
Note You need to log in before you can comment on or make changes to this bug.