Issue metadata
Sign in to add a comment
|
Composited <foreignObject> under nested SVG with offset paints at wrong location
Reported by
ashishgu...@gmail.com,
Jun 6 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.170 Safari/537.36 OPR/53.0.2907.68 (Edition Campaign 76) Steps to reproduce the problem: 1. Open the attached Test.html, canvas is rendered at incorrect location. 2. Open chrome://flags and disable canvas hardware accelerated rendering. Problem goes away. 3. This behavior is specifically happens when foreignobject is used in SVG. What is the expected behavior? What went wrong? Canvas position is not respected while rendering the drawing when GPU acceleration for canvas is enabled. This issue goes away when canvas GPU acceleration is disabled. Did this work before? No Does this work in other browsers? Yes Chrome version: 67.0.3396.79 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 29.0 r0 In chromium 66 canvas location was not correct either when used in foreignobject, which got corrected in chromium 67.
,
Jun 7 2018
Sounds like M67 made it better, but it's still not fully correct. Will investigate.
,
Jun 7 2018
Thanks for assigning this issue. This issue effects all OS: Verified the existence of this issue on Linux (Ubuntu) and Mac for version 67.0.3396.79.
,
Jun 18 2018
This bug is similar to the one found here. https://bugs.chromium.org/p/chromium/issues/detail?id=467484
,
Jul 10
Adjusted example attached that does not use canvas. The issue has to do with nested <svg> tags, where the inner one has an x and a y.
,
Jul 23
Is there a time line where you are targeting to resolve this issue. We have HMI product which fails render canvas based charting. Here is the link to product page https://selinc.com/products/5035/
,
Jul 23
There is no timeline yet, sorry.
,
Jul 23
,
Jul 23
This issue will be fixed by code changes currently under development. Unfortunately <foreignObject> has been broken in various ways for a long time, but we are finally fixing it. The changes will hopefully roll out to all users in the next few months.
,
Jul 25
Thanks ! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by gov...@chromium.org
, Jun 6 2018Labels: Needs-Triage-M67