New issue
Advanced search Search tips

Issue 821451 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

SVG Rendering

Reported by nluss...@globalia.ca, Mar 13 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36

Steps to reproduce the problem:
With SVG 1.1
Create a rectangle
svg.rect(10, 20).fill('relative/path/to/image.png').transform({
  x: 20,
  y: 20
});

<svg id="SvgjsSvg1012" xmlns="http://www.w3.org/2000/svg" version="1.1" width="638.625" height="430.5" xmlns:xlink="http://www.w3.org/1999/xlink"><rect id="SvgjsRect1063" width="491.25" height="320" fill="url(#SvgjsPattern1065)" transform="translate(16.375 24.599999999999998)"></rect><defs id="SvgjsDefs1013"><pattern id="SvgjsPattern1065" x="0" y="0" width="32" height="32" patternUnits="userSpaceOnUse"><image id="SvgjsImage1064" xlink:href="/img/pattern.png" width="32" height="32"></image></pattern></defs></svg>

What is the expected behavior?
See the pattern.

What went wrong?
Nothing show up.

Did this work before? Yes 64

Chrome version: 65.0.3325.146  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 
Labels: Needs-Bisect Needs-Triage-M65
Labels: Triaged-ET Needs-Feedback
Tested the issue on chrome reported version 65.0.3325.146 using windows-7 with steps mentioned below:
1) Launched chrome reported version and navigated to URL: https://www.w3schools.com/graphics/tryit.asp?filename=trysvg_rect3
2) On the loaded page, removed the existing code and pasted the code provided in comment#0( i.e., <svg id="SvgjsSvg1012" xmlns="http://www.w3.org/2000/svg" version="1.1" width="638.625" height="430.5" xmlns:xlink="http://www.w3.org/1999/xlink"><rect id="SvgjsRect1063" width="491.25" height="320" fill="url(#SvgjsPattern1065)" transform="translate(16.375 24.599999999999998)"></rect><defs id="SvgjsDefs1013"><pattern id="SvgjsPattern1065" x="0" y="0" width="32" height="32" patternUnits="userSpaceOnUse"><image id="SvgjsImage1064" xlink:href="/img/pattern.png" width="32" height="32"></image></pattern></defs></svg>) and clicked on "RUN"
3) On right hand side able to see some pattern(set of squares)

@Reporter: Please find the attached screen cast for your reference and let us know if we missed anything in reproducing the issue, provide your feedback on it which helps us in further triaging it in better way. If possible could you please provide sample URL/test file for further triaging.

Thanks!
821451.mp4
1.2 MB View Download
I forgot to mention that the SVG is dynamically generated in Javascript with SVG.js library. It works correctly on Chrome Canary (version 67).

Thanks!
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 14 2018

Cc: viswa.karala@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
@Reporter: from the comment#3 we are not sure the issue is reproducible or not, with the process we have mentioned in comment#2, we are able to see the pattern(as captured in comment#2 screen cast) in reported version and latest canary. if possible could you please provide the test file/URL which will reproduce the issue and provide the screen cast of excepted behaviour which helps us in further triaging it in better way.

Thanks!
The bug is fixed. It was a CSS transition that was causing the rendering problem. Thank you very much for your excellent support!
Project Member

Comment 7 by sheriffbot@chromium.org, Mar 17 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Bisect
Status: WontFix (was: Unconfirmed)
As per comment#6 from the reporterr, as the issue has been fixed, hence closing it and marking it as won't fix.

Thanks!

Sign in to add a comment