Bug 41304

Summary: Drawing border-radius from path should try to make corners symmetrical with dashed and dotted styles
Product: WebKit Reporter: Beth Dakin <bdakin>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: ahmad.saleem792, ap, bdakin, bfulgham, mitz, rniwa, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   
Attachments:
Description Flags
Test case
none
All browsers differs from each other none

Beth Dakin
Reported 2010-06-28 14:17:31 PDT
Created attachment 59940 [details] Test case http://trac.webkit.org/changeset/62035 introduced a new method of drawing border-radius using paths. Right now, this new code is only enabled for some platforms…if you want to know if your favorite platform has the new code path enabled, see if it has been added to #define HAVE_PATH_BASED_BORDER_RADIUS_DRAWING in RenderObject.h. Here is what the spec says: "Note: There is no control over the spacing of the dots and dashes, nor over the length of the dashes. Implementations are encouraged to choose a spacing that makes the corners symmetrical." Right now, our corners for dashes and dotted borders when drawn with the new method are not always symmetrical. Attached is a test case demonstrating a time when they are not symmetrical.
Attachments
Test case (321 bytes, text/html)
2010-06-28 14:17 PDT, Beth Dakin 		no flags
Details
All browsers differs from each other (1.41 MB, image/png)
2022-07-23 07:28 PDT, Ahmad Saleem 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Ahmad Saleem
Comment 1 2022-07-23 07:28:05 PDT
Created attachment 461156 [details] All browsers differs from each other I am able to reproduce this bug in Safari 15.6 on macOS 12.5 using attached test case and as can be seen from attached screenshot - Safari and Chrome have overlap little bit but Firefox renders this fine. Thanks!
Radar WebKit Bug Importer
Comment 2 2022-07-23 11:58:57 PDT
<rdar://problem/97489006>
Note You need to log in before you can comment on or make changes to this bug.