The browser's interpretation of the 'opacity' CSS attribute has become much lighter
Reported by
jha...@23andme.com,
Nov 3 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36 Steps to reproduce the problem: 1. Style an element on a page with 'opacity: .1' in the current version of Chrome 2. Do the same in chrome v53 or older. 3. Compare the two and note that the current version has a much lighter shade. What is the expected behavior? The shade of opacity is much lighter than prior versions of chrome and compared to other browsers. The opacity at .1 should be consistent with what it was before. What went wrong? The browser's interpretation of opacity has become too light. Did this work before? N/A Chrome version: 54.0.2840.87 Channel: stable OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 23.0 r0
,
Nov 4 2016
,
Apr 5 2017
Here is a test case according to the original report: https://jsfiddle.net/mrteemwL/ Test team - can you please confirm that behaviour changes from m53 to m54 on Mac OSX per the report? Also, this seems like it would be a Paint issue, not a Style issue.
,
Apr 5 2017
Opacity like this is either raster or compositor. Since we're on Mac it may even be the switch to surfaces.
,
Apr 6 2017
Unable to reproduce the issue on MacBook Air-10.12.3,Mac Retina-10.12.3 ,Window-7 and Linux Ubuntu-14.04 using chrome stable version 57.0.2987.133 & canary 59.0.3063.0 and reported version 54.0.2840.87 & 53.0.2744.0 and 54.0.2840.0 with given file from comment#4. And also not observed any behavior changes from M53 to M54. Please find the attached screenshots for reference. Thanks.
,
Apr 29 2017
Could the issue be GPU raster? I believe it shipped in M54 on the Mac.
,
Jun 16 2017
Maybe a monitor calibration issue? Giving the translucent div a white background shows the color to me as 90% red/green using the color meter, which seems correct for an opacity of 0.1 of blue. So if we did something different before, it was probably wrong.
,
Jun 16 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by krajshree@chromium.org
, Nov 4 2016Labels: Needs-Feedback