83189 2012-04-04 12:07:58 -0700 Canvas inside SVG(foreignObject) positioning error 2022-06-01 19:37:25 -0700 1 1 1 Unclassified WebKit SVG 420+ Mac (Intel) OS X 10.6 RESOLVED DUPLICATE 23113 InRadar P2 Normal --- 0 olivier_lamothe webkit-unassigned ahmad.saleem792 dmitrijs.balcers sabouhallawa simon.fraser webkit-bug-importer zimmermann oldest_to_newest 595775 0 olivier_lamothe 2012-04-04 12:07:58 -0700 Overview A positioning error occur when a canvas is placed inside a foreignObject tag. If the canvas is drawn with hardware acceleration , the transform attribute is not applied correctly. Probably related in some way to : https://bugs.webkit.org/show_bug.cgi?id=71819 Step to reproduce : Go to : http://jsfiddle.net/olamothe/QZRf3/ Change the canvas width between 256<-->257 Actual results : The transform attribute is not applied correctly when the canvas size is over 257. Canvas is moved to (0,0) Expected results : Canvas should always be at (100,100) I.E : the transform-translate attribute Additional information : Chrome 18.0.1025.142 Mac OS X 10.6.8 The underlying problem is not really the canvas size, it's actually when the canvas is being rendered with the aid of the hardware. It just so happen that in chrome 18 , canvas over 256 pixel in width or height are rendered with the aid of the GPU. The same effect can be achieved with safari 5.1.5 if you force it to render with hardware ( eg : -webkit-transform : translateZ(0) ) It is also not only linked to the canvas tag. For example if you replace the canvas with a div in the jsfiddle , and apply a CSS 3d transform, the same thing happen. 1861416 1 dmitrijs.balcers 2022-04-14 01:24:33 -0700 I have reproduced the same issue. 1873424 2 ahmad.saleem792 2022-06-01 16:24:53 -0700 I am still able to reproduce this using attached test case in Safari 15.5 and Safari Technical Preview 146 on macOS 12.4. Thanks! 1873465 3 webkit-bug-importer 2022-06-01 18:36:35 -0700 <rdar://problem/94259941> 1873499 4 simon.fraser 2022-06-01 19:37:25 -0700 *** This bug has been marked as a duplicate of bug 23113 ***