Regression: Killed plug-in window appears broken while scrolling up/down.
Reported by
shruti.j...@etouch.net,
Mar 9 2018
|
|||||
Issue descriptionChrome Version:66.0.3359.22 Revision 37c99647fccce6a8929b1ddebbcdfbe6148dea43-refs/branch-heads/3359@{#126}(32/64 bit) OS: Windows(7,8,8.1,10), Linux(14.04 LTS) and MAC (10.12.6,10.13.1,10.13.4) Test URL:http://www.shockwave.com/gamelanding/daily-spot-the-pic-bonus.jsp Steps to reproduce: (1) Launch chrome and navigate to above URL (2) Click on ‘Allow’ flash and navigate to task manager from wrench icon. (3) From task manager End process :’plugin: shockwave flash’ and scroll up/down page and observe. Actual Result:Killed plug-in window appears broken while scrolling up/down. Expected Result:Killed plug-in window should not appear broken while scrolling up/down. This is a regression issue broken in “M-66” and using per-revision bisect providing the bisect results, Good Build:66.0.3344.0 (Revision:535593) Bad Build:66.0.3345.0 (Revision:536026) You are probably looking for a change made after 535635 (known good), but no later than 535637 (first known bad). CHANGE-LOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/e04a14f4769d6b33b32686ccc3414e917a625ae7..a5676deb1e679035678bc1ed997518cd226378b9 Suspect:https://chromium.googlesource.com/chromium/src/+/96f85b68747a679ea1ac4cd05d6743ae5f7142b7 @Steve Kobes: 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: Issue is also reproducible in Dev #66.0.3359.15, 66.0.3359.23 (PGO), Stable #65.0.3325.146 and Beta #65.0.3325.124 build. Thank You!
,
Mar 10 2018
,
Mar 15 2018
Unable to repro in current canary (67.0.3371.0). Testers: can you please verify that the issue is fixed?
,
Mar 16 2018
With respect to comment#3: Rechecked the above issue on Latest Canary build #67.0.3372.0 on Windows(7,8,8.1,10),Linux(14.04 LTS) and MAC (10.12.6,10.13.1,10.13.4) and issue is working as intended. Thank You!
,
Mar 16 2018
Closing per #4 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by skobes@chromium.org
, Mar 9 2018Labels: -Pri-1 Pri-2