Issue metadata
Sign in to add a comment
|
Canvas transform is reset when drawImage
Reported by
bengjing...@goanimate.com,
Feb 8 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: 1. Create a offscreen canvas 2. Create context, add transform to it 3. Call drawImage with HTMLCanvasElement What is the expected behavior? The canvas should be rendered with current transform What went wrong? The transform was reset. Canvas render it with new transform. After that, the transform was gone forever. Did this work before? Yes Probably Chrome 62 Does this work in other browsers? Yes Chrome version: 64.0.3282.140 Channel: stable OS Version: OS X 10.12.6 Flash Version: No
,
Feb 9 2018
bengjing.chen@ Thanks for the issue. Request you to provide the URL where this issue can be reproduced, which will help in further triaging. Thanks..
,
Feb 11 2018
Hi, for some reason we are not able to provide the URL to the bug, I can only provide some other findings, if that doesn't help, please suspend this or mark this as low priority. 1. Confirm this only happens on Chrome 64, not 63 and 65 (dev version) 2. Might relate to GPU acceleration (Tried with GPU acceleration flag disabled and it works correctly) 3. Sometimes fillRect before drawImage are also at the incorrect position. Not sure if it is because the transform is not applied or fillRect also trigger the reset transform. 4. Can not be reproduced with jsfiddle. But this is can be constantly reproduced in certain circumstances. (just like the site I report) 5. Even this can be constantly reproduced in certain circumstances, it still happens randomly. For canvas application using requestAnimationFrame, it happens most of the time, but also gave correct result some times.
,
Feb 11 2018
Thank you for providing more feedback. Adding requester "susanjunia.boorgula@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 13 2018
@xlai: I think this might be a duplicate of a bug you fixed recently. PTAL
,
Feb 13 2018
Yes, this issue should be fixed in the next update of Chrome 64. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Feb 8 2018