RESOLVED CONFIGURATION CHANGED257026
SVG rendering error at path 
https://bugs.webkit.org/show_bug.cgi?id=257026
Summary SVG rendering error at path
Matt Sephton
Reported 2023-05-19 06:45:24 PDT
Created attachment 466417 [details] safari 16-5 on 12-6-6 non-retina SVG rendering error on both non-Retina and Retina displays. There are notches taken out of the path Seen in - Safari 16.4 on macOS 12.6.5 Monterey - Safari 16.4 on macOS 12.6.6 Monterey - Safari 16.5 on macOS 12.6.6 Monterey Not seen in - Safari Tech Preview 170 on macOS 12.6.5 Monterey - Safari Tech Preview 170 on macOS 12.6.6 Monterey
Attachments
safari 16-5 on 12-6-6 non-retina (8.79 KB, image/png)
2023-05-19 06:45 PDT, Matt Sephton 		no flags
Details
safari 16-5 on 12-6-6 retina (61.99 KB, image/png)
2023-05-19 06:45 PDT, Matt Sephton 		no flags
Details
no problem safari tech preview on 12-6-6 non-retina (8.53 KB, image/png)
2023-05-19 06:46 PDT, Matt Sephton 		no flags
Details
the SVG in question (4.64 KB, image/svg+xml)
2023-05-19 06:46 PDT, Matt Sephton 		no flags
Details
what the SVG paths look like (57.32 KB, image/png)
2023-05-19 06:46 PDT, Matt Sephton 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Matt Sephton
Comment 1 2023-05-19 06:45:43 PDT
Created attachment 466418 [details] safari 16-5 on 12-6-6 retina
Matt Sephton
Comment 2 2023-05-19 06:46:11 PDT
Created attachment 466419 [details] no problem safari tech preview on 12-6-6 non-retina
Matt Sephton
Comment 3 2023-05-19 06:46:31 PDT
Created attachment 466420 [details] the SVG in question
Matt Sephton
Comment 4 2023-05-19 06:46:44 PDT
Created attachment 466421 [details] what the SVG paths look like
Alexey Proskuryakov
Comment 5 2023-05-22 10:34:41 PDT
Thank you for the report! Given that it's happening in shipping Safari but not in STP, seems like this is already fixed in WebKit.
Matt Sephton
Comment 6 2023-05-22 18:54:04 PDT
Thanks for the info! I always assumed shipping Safari or Technology Preview would use latest WebKit at the date of shipping,
Note You need to log in before you can comment on or make changes to this bug.