Issue metadata
Sign in to add a comment
|
Regression: Flickering of extension overlay is seen while opening the drop down list.
Reported by
sanyam.g...@etouch.net,
Oct 26
|
||||||||||||||||||||||
Issue descriptionChrome Version : 72.0.3592.0 (Official Build)Revision 3274d2b27158c8f54008ac69629235202f28f306-refs/branch-heads/3592@{#1}(32/64-bit) OS : Mac(10.13.1, 10.13.6) Test URL: https://chrome.google.com/webstore/detail/vidiq-vision-for-youtube/pachckjkecffpdphbpmfolblodfkgbhl/related?utm_source=chrome-ntp-icon Steps to reproduce: 1. Launch chrome with above mentioned extension. 2. Navigate to NTP , click on Extension icon to open the overlay. 3. Click on 'YouTube shortcuts' to open drop down list and observe. Actual Result : Flickering of overlay is seen while opening the drop down list. Expected Result: No such flickering should be seen. This is a regression issue, broken in 'M-72', and below is the chromium bisect info: Good Build: 72.0.3582.0 (Revision: 599848) Bad Build : 72.0.3583.0 (Revision: 600163) You are probably looking for a change made after 599957 (known good), but no later than 599967 (first known bad). Chromium bisect URL: https://chromium.googlesource.com/chromium/src/+log/35a1e5fcd4c38b09b5dcbd81d7cac6c06c2f6337..d9727e94dad3174e8fd3224eb775a121718cbeee Suspecting: r599961 or r599963 ? @ellyjones: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: 1.Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect" error message. 2.Tried on other machines but still getting the same error again. 3.Issue is not reproducible on Windows(7, 8, 8.1 ,10), Mac (10.14.1) and Linux (14.04 LTS) Thank You..!
,
Oct 29
Doubtful, my CL should only have an effect on Android. Perhaps the v8 roll?
,
Oct 29
Kicking this over to ccameron@ for gpu I guess.
,
Nov 28
This looks to be an issue with window resizing (+sdy), but this is working 72.0.3623.0, and it worked ... so perhaps this is fixed? I don't see a more likely culprit in the regression range (maaaybe r599960, since it's related to the blocking that we do for resize?). But marking as fixed cause this looks to be working ATM. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ellyjo...@chromium.org
, Oct 29