Fill in SVG path rendered incorrectly as gradient if rounded corners are used
Reported by
jan.pete...@googlemail.com,
Mar 20 2018
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: 1. Open the HTML document attached. 2. The SVG documents are identical except for the use of a C-drawing command in the upper one. The Front and Back parts of the SVG have the same CSS class attached in both SVGs. 3. When using C drawing commands the fill is rendered as a gradient, where it should be a solid fill as in the second image. What is the expected behavior? The fill should be solid independent of C-commands in the path. What went wrong? The fill is incorrectly rendered as a gradient. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 64.0.3282.186 Channel: stable OS Version: OS X 10.13.3 Flash Version:
,
Mar 20 2018
,
Mar 20 2018
,
Mar 20 2018
,
Apr 2 2018
The NextAction date has arrived: 2018-04-02
,
Apr 2 2018
WontFix due to lack of feedback. We're waiting on information about the GPU rendering state. We can re-open if new information becomes available.
,
Apr 12 2018
Sorry, just noticed that replying to this thread via email is not working. Yes, hardware acceleration was enabled and the issue disappears once I disabled it.
,
Apr 12 2018
Thanks for getting back to us. Over to the GPU raster team.
,
May 14 2018
Mac triage: assigning directly to danakj@ cc enne@ for GPU triage.
,
May 14 2018
This sounds like a gpu rasterization issue.
,
May 14 2018
Does this reproduce on Canary? I wasn't able to reproduce on a local build. I'm wondering if this was fixed by any of Stephen's tessellating path renderer changes. This SVG does trigger the tessellator.
,
May 15 2018
This does appear to be fixed. bisect-builds says: https://chromium.googlesource.com/chromium/src/+log/5b2de20541d2b08bf64e81804b538eb4d03a4e21..8b9799f3477553ff169933c5007cca6d4a29c21c which includes https://chromium.googlesource.com/chromium/src/+/e4d6d0b50ec2e40aabe6a8c9928f512101771bb1 (Here are the params i used, because bisect was kind of annoying due to GPU raster being blacklisted on my machine during the fix window: tools/bisect-builds.py --use-local-cache --archive mac --good 555728 --bad 400000 -- --no-first-run file:///Users/senorblanco/Downloads/testcase.html --gpu-rasterization-msaa-sample-count=0 --show-fps-counter --ignore-gpu-blacklist) If you still see this issue, please re-open. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by f...@opera.com
, Mar 20 2018