Chromium sometimes fails to render SVGs dynamically added to the DOM until' something triggers a relayout.
Reported by
elitesci...@gmail.com,
Dec 11
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: 1. Dynamically Add SVG to DOM 2. 3. What is the expected behavior? SVG To display What went wrong? Sometimes SVGs do not display until' a layout change causes the browser to redraw. Once that SVG is drawn it appears that the browser can draw the same svg without problems. Did this work before? Yes Does this work in other browsers? Yes Chrome version: 70.0.3538.110 Channel: stable OS Version: 10.0 Flash Version:
,
Dec 12
,
Dec 14
The application can be accessed at: http://cloud.finplatform.com:8083/finMobile/google User: google Pass: chrome Once you're logged in click the hamburger icon at hte top left. Click "Graphics Builder" which is the button in the 3rd row and 3rd column. Once the graphics builder opens either click the open icon or click "BUILDER" then "Open Graphic". There is only one graphic there named "Test Graphic" click it then click open. Now you'll see a components panel on the left side. scroll down to the "SIEMENS|2D AIR" category. All of these are SVG Assets. drag out the first one named "2D AHU COMPONENT ALL". This one exhibits that behavior. Some will and some wont. Once a component is drawn the first time, subsequent drags will work with no problem. which means you may have to refresh the browser to get it to happen again.
,
Dec 14
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
,
Dec 17
Able to reproduce the issue on chromium version #70.0.3538.110, latest chrome stable #71.0.3578.98 and latest chrome #73.0.3642.0 using as per steps mentioned in comment #3. The behaviour is observed from old M-60 builds(#60.0.3112.113). This is non-regression issue hence marking it as untriaged and requesting someone from dev team to look into the issue. Thanks.!
,
Dec 17
Thanks for the test case.
,
Dec 17
,
Dec 17
No problem. And thank you.
,
Dec 25
The NextAction date has arrived: 2018-12-25
,
Dec 26
,
Jan 7
The NextAction date has arrived: 2019-01-07
,
Jan 7
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by schenney@chromium.org
, Dec 11Labels: Needs-Feedback
NextAction: 2018-12-25