New issue 108406 by am...@google.com: SVG anti-aliasing is not working
property in Chrome 16.0.912.63 beta on Linux
http://code.google.com/p/chromium/issues/detail?id=108406
Chrome Version : 16.0.912.63
OS Version:
URLs (if applicable) :
Other browsers tested:
Safari 5: OK
Firefox 9.x: OK
What steps will reproduce the problem?
1. Open the attached SVG file in Chrome 16.0.912.63 *beta* on Linux.
2. The lines are "pixelized" and have less anti-aliasing that usually.
What is the expected result?
The lines should be anti-aliased and look smooth.
In Chrome 16.0.912.63 (without the beta) on mac this works fine. Also it
works fine on Safari on mac and Firefox 9 on Linux. Haven't tried Chrome
16.0.912.63 on Linux (without the beta).
What happens instead?
The lines are pixelized and not smooth.
UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.7 (KHTML,
like Gecko) Chrome/16.0.912.63 Safari/535.7
Attachments:
chrome_pixels.svg 49.8 KB
Just checked it on version 15.0.874.121 and 16.0.912.63 (not beta) for
Linux and it also fails so this is not related to the latest version.
On windows it also fails.
In general it seems that this doesn't happen all the time as we haven't
noticed it until now. We will try to isolate the cause a bit more.
Comment #2 on issue 108406 by jer...@chromium.org: SVG anti-aliasing is not
working property in Chrome 16.0.912.63 beta on Linux
http://code.google.com/p/chromium/issues/detail?id=108406
Amit: Can you try a Chrome Canary build on Mac and see if it happens there?
Greg, Levi: Do you think this might be in Skia? Any idea who can look at
this?
We have isolated the problem as much as possible.
Attached are two svg files which differ by very little - adding a single
point to each of the two visible path elements. This extra point increases
the path segments to be 250 so it seems like something strange happens
exactly when there are 250 path segments (or more) - the anti-aliasing
stops working.
Also, notice that we are using a cropping window so this extra point, and
in fact most of the points, are not in the visible area. The image itself
should not have been changed.
Attachments:
c1.svg 13.3 KB
c2.svg 13.3 KB
Comment #4 on issue 108406 by jer...@chromium.org: SVG anti-aliasing is not
working property in Chrome 16.0.912.63 beta on Linux
http://code.google.com/p/chromium/issues/detail?id=108406
epoger: Looks like this is a regression, at least on Mac. Do you know who
can look at this in Skia-land ?
Results testing on Mac:
Canary 18.0.978.0: Both c1.svg and c2.svg are NOT antialiased.
Dev 17.0.963.12: both ARE aliased and look nice :)
So it looks like there's a good chance this bug is in Skia and represents a
regression on OS X. Marking as such.
Has anyone had a chance to look some more into this issue?
Comment #6 on issue 108406 by epo...@google.com: SVG anti-aliasing is not
working property in Chrome 16.0.912.63 beta on Linux
http://code.google.com/p/chromium/issues/detail?id=108406
Sorry about missing this bug in the blurry time just before Christmas.
I will work on reproducing this bug in various builds later this morning,
and update this bug afterwards.
I see that the bug was narrowed down to something very specific. Do you
think there would be a solution in the upcoming Chrome versions or should
we try to avoid this situations altogether in our product as much as
possible?
I'm having a tough time with this as well. Need better aliasing for my
background image that accommodates all zoom levels.