Bug 152003 - SVG Clipping artifacts
Summary: SVG Clipping artifacts
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: Safari 9
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-08 11:22 PST by Zoltan Horvath
Modified: 2022-07-14 11:50 PDT (History)
8 users (show)

See Also:


Attachments
Sample svg (954 bytes, image/svg+xml)
2015-12-08 11:22 PST, Zoltan Horvath
no flags Details
Screenshot (24.47 KB, image/png)
2015-12-08 11:22 PST, Zoltan Horvath
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Zoltan Horvath 2015-12-08 11:22:40 PST
Created attachment 266914 [details]
Sample svg

Within SVG:

* Add an object with a light color
* Add an white object which overlaps with the previous one
* Apply an ellipse as a clip mask on them.

Over the white background shape the clip mask leaves a hairy line, see screenshot.
Comment 1 Zoltan Horvath 2015-12-08 11:22:57 PST
Created attachment 266915 [details]
Screenshot
Comment 2 Zoltan Horvath 2015-12-08 11:23:28 PST
Same bug happens in Chromium: https://code.google.com/p/chromium/issues/detail?id=567811
Comment 3 Dirk Schulze 2016-10-12 06:30:55 PDT
This could be caused by 2 things:
1) Normal AntiAliasing issue that could be fixed if we would support crisp-edges in WebKit
2) The way we generate the rendered path from the ellipse data.

Zoltan could you try converting the ellipses to paths and check if you still see this issue?
Comment 4 Ahmad Saleem 2022-07-14 09:48:21 PDT
I am unable to reproduce clipping issue where the bottom grey arc was clipped but hairy line exist across all browsers but it is quite subtle in other browser (thin) but it is just matter of few pixels.

I think considering "clipping" is resolved and no longer present in Safari 15.5 on macOS 12.4 while hairy line is consistent across all browsers (Chrome Canary 105 and Firefox Nightly 104) except bit thin. I think we can consider it as RESOLVED CONFIGURATION CHANGED due to fixed along the way. Thanks!
Comment 5 Ryosuke Niwa 2022-07-14 11:50:52 PDT
Yeah, config changed.