Issue metadata
Sign in to add a comment
|
CSS opacity bug in v61.0.3163.100
Reported by
edaa...@gmail.com,
Oct 13 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. See my JSFIDDLE example 2. https://jsfiddle.net/ctqs189f/5/ 3. Everyting will be clear What is the expected behavior? See my JSFiddle. What went wrong? https://jsfiddle.net/ctqs189f/5/ Check this JSFiddle with version 61.0.3163.100 (64bits) and everything will be clear. Did this work before? Yes Don't know exactly, but it's a recent bug Chrome version: 61.0.3163.100 Channel: stable OS Version: 10.0 Flash Version: Yes, there is a very similar bug with CSS box-shadow.
,
Oct 13 2017
On my home PC I have no issues either with the same version of Chrome. But @ work both me and my colleague have the same glitch. Check the screenshot I just made using VPN and then RDP to connect to my office PC.
,
Oct 13 2017
It only apears in Chrome and just recently. Firefox, IE and IE Edge all work fine. Me and my colleague both have the same hardware but different versions of Windows 10 (x64). Could it be videocard related?
,
Oct 15 2017
Yes, we have experienced the same bug on Windows 10 and Chrome. In our case a simple div with a background color changes color when vertically scrolling. The div also gets more than one color in there and sometimes it gets smaller boxes inside rectangle as the last screenshot above. This issue showed up for us around Wed Oct 11, 2017 and it seems like a video card/buffer issue. As it only happens when we do vertical scroll perhaps it is related to that as well.
,
Oct 16 2017
,
Oct 16 2017
Can confirm on 63.0.3226.2 (canary) and on 61.0.3163.100 (stable)
,
Oct 16 2017
Able to reproduce the issue on Windows 10 with chrome stable #61.0.3163.100, but not on Beta #62.0.3202.52, Dev #63.0.3236.0, Canary #63.0.3239.6 Issue is broken in M61 branch builds. Bisect Info: =========== Good build : 61.0.3163.43, Bad build : 61.0.3163.44, The following CL's between good and bad build versions =========================================== https://chromium.googlesource.com/chromium/src/+log/61.0.3163.43..61.0.3163.44?pretty=fuller&n=10000 The suspecting Change Log is : ----------- https://chromium.googlesource.com/chromium/src/+/9f18454c2bf68b6895308940b4ac2c9249921b9a Note: 1. Since it only reproducible on Stable build, hence adding RB-Stable label 2. Not able to repro on Ubuntu 14.04 & Mac 10.12.6 enne@- Could you please look into this issue, if it's related to your change? if not could you please help us to reassign this issue to the right owner.
,
Oct 16 2017
,
Oct 16 2017
Attaching the screenshots for comment #7
,
Oct 16 2017
I would change the priority to emergency (0) instead of want (2) because this is breaking a lot of web apps !!! Just take a look at the video below. Notice that the colored rectangles change colors when scrolling and sometimes they get multiple colors where it should only had been 1. I can provide log in access to help debug the issue. We are getting lots of customers complains, specially considering that we are a startup and tell customers that we only test on Chrome.
,
Oct 16 2017
I presume this is another manifestation of the clear buffer bug. Robert, do you think so? Reporters, please help us out by doing the following: 1) go to chrome://gpu and paste the output into this bug report. 2) Try Chrome Canary and see if the problem is fixed there.
,
Oct 16 2017
Responding to #11, I do believe it is a duplicate of crbug.com/768134 . I bisected the bug (and its fix) to the range: https://chromium.googlesource.com/chromium/src//+log/f820527ed71a..e04d39989fc5 which includes a Skia roll which, in turn, includes: https://skia-review.googlesource.com/55381 (Always use draws instead of clears for ANGLE D3D11) Which is the fix for crbug.com/768134 . Note, that this fix has been cherry-picked back to M62 (62.0.3202.48 and above) but will not be cherry-picked back to M61.
,
Oct 16 2017
Here is the chrome://gpu output as requested above. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by bokan@chromium.org
, Oct 13 201771.4 KB
71.4 KB View Download