Wrong color displayed when setting transform: translate3d(0px, 0px, 0px);
Reported by
jan.boes...@incors.com,
Dec 4 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Example URL: https://codepen.io/anon/pen/MOxOLm?editors=1010 Steps to reproduce the problem: 1. Open the codepen at https://codepen.io/anon/pen/MOxOLm?editors=1010 Alternatively you can open the attached html file. This displays two canvases on a dark div. Both canvases are filled with one and the same translucent color. The only difference between the canvases is that one has set the attribute style="transform: translate3d(0px, 0px, 0px);" A real-life case can be seen by following this url: https://www.iconfu.com/main#/icons/5/1/141/ff9650-0-0:ff6400/1:ff9650//191919 What is the expected behavior? The two canvases (the greenish squares) should have the same color (see attached expected_result.png). What went wrong? The colors are different. The canvas with the transform applied shows a wrong color (see attached actual_result.png). Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I was not able to reproduce the behaviour on othr browsers (Firefox, InternetExplorer) or on a macbook pro.
,
Dec 5 2017
Unable to reproduce this issue on reported version 62.0.3202.94 and on latest canary 65.0.3284.0 using Windows 7 and Windows 10 with steps mentioned below. 1. Navigated to chrome://flags and searched for #force-color-profile and is seen as default. 2. Now navigated to https://codepen.io/anon/pen/MOxOLm?editors=1010 and observed same color on both the squares. Attaching screencast for reference. @Reporter: Could you please chck the video and let us know if we miss anything from steps. Please guide us with screencast for further triaging of this issue. Thanks!
,
Dec 5 2017
Thanks for looking into this. I installed the latest Canary earlier today and since then I have not been able to reproduce the issue even on the production build 62.0.3202.94. This is the only change to my system since I reported the issue, so it seems like updating Canary somehow influenced the production build. Not sure if this makes sense.
,
Dec 5 2017
Thank you for providing more feedback. Adding requester "sc00335628@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
,
Dec 5 2017
After trying some more the issue appeared again, but this time only in Canary. In the production build the issue is still not reproducable. Unfortunately it seems that even I cannot reliably reproduce the issue, therefore it may become difficult to fix this.
,
Dec 5 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by jan.boes...@incors.com
, Dec 5 2017