Traces of selector are left behind above windows in Alt+Tab |
||||
Issue descriptionVersion: 54.0.2840.13 (Dev) OS: Chrome OS What steps will reproduce the problem? (1) Have more than 2 windows on screen (2) Alt+Tab (3) Shift+Alt+Tab to return to the first window What is the expected output? First window selected, no trace of selector on the second window What do you see instead? First window selected but traces of the selector widget remain after animation (look closely at the Downloads caption in attached screenshot). Please use labels and text to provide additional information. Looks like individual animation frames leave some pattern behind. I am not seeing this in simulation build, only on device. Also no seeing this when the window tiles move behind the selector as part of Alt+Tab sequence.
,
Sep 28 2016
I no longer see this in 54.0.2840.33. Could https://codereview.chromium.org/2333323003/ (merged in M-54) have fixed this?
,
Sep 28 2016
that would not surprise me.
,
Sep 28 2016
Would it be possible to confirm, so that if we ever revert that change (if and when the blur is optimized), we won't introduce a regression?
,
Sep 28 2016
How would we confirm that? Merge the blur back in and see if the problem comes back? :) If you're asking for a regression test, I have no idea how we'd write a test for this anyway. +mdm was seeing this issue. Mike, is it resolved for you now (on 54.0.2840.33 or newer)?
,
Sep 29 2016
I was thinking local revert, build, deploy and try that local build on a device if you have access to a Chrome OS device. This may not be the easiest though.
,
Sep 30 2016
I could reproduce this with 54.0.2840.24, but no longer on 54.0.2840.43.
,
Oct 4 2016
,
Nov 8 2016
Issue 645016 has been merged into this issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by varkha@chromium.org
, Sep 9 20161.6 MB
1.6 MB View Download