Regression:Original window stays in background after clicking on popout option
Reported by
vineetha...@etouch.net,
Apr 20 2018
|
|||||||||||
Issue descriptionChrome version : 67.0.3396.13 (Official Build) b3152cbcc026b1404e0a4bcd161244bcf009650b-refs/branch-heads/3396@{#152}(32/64 bit) OS : Windows(7,8,8.1,10), Mac(10.12.6,10.13.1,10.13.5) and Linux(14.04 LTS) OS URL: https://chrome.google.com/webstore/search/Chrome%20IG%20Story?hl=en-GB Pre-condition: Should be logged in to https://www.instagram.com with valid credentials. What steps will reproduce the problem? (1) Launch Chrome, navigate to above URL and add 'Chrome IG Story' chrome extension. (2) Click on the Chrome IG extension icon near the omnibox to open the extension overlay. (3) Click on the 'Popout' icon present in the overlay and observe. Actual Result: After window is popped out, original window also stays and does not get closed. Expected Result: After window is popped out , original window should get closed. This is regression issue broken in ‘M-66’ and providing the bisect using per-revision bisect, Good build: 66.0.3350.0(Revision: 537343) Bad build: 66.0.3352.0(Revision: 538313) You are probably looking for a change made after 538034 (known good), but no later than 538035 (first known bad). CHANGELOG 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/fe5ae1bdbc095e41042faf99cf4512c08464d645..86f94f52fd03c969761243b197bdbbb12f4da769 Suspect: https://chromium.googlesource.com/chromium/src/+/86f94f52fd03c969761243b197bdbbb12f4da769 @robliao: 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. Thank You!
,
May 30 2018
,
May 30 2018
Does this repro on Windows?
,
May 30 2018
Are we targeting this fix for M68 Beta experiment?
,
May 30 2018
I don't think so. This is likely the same behavior encountered on Windows. It has a FoundIn-66 label, so it shouldn't affect M68 Beta.
,
May 30 2018
Ok, thank you. It is currently marked as P1 and "Target-68" label is also applied to wanted to make sure.
,
May 30 2018
Update with respect to Comment#3: Rechecked the above issue on Windows 10 OS for latest Canary build #69.0.3445.0 and observed that the issue is reproducible on Windows also. Please refer attached screen cast for the same.
,
May 30 2018
,
May 30 2018
Thanks for the confirmation. Changing the priority as Windows has this behavior already (and like has had it since near the beginning).
,
Jun 20 2018
,
Jun 20 2018
,
Jun 28 2018
,
Jul 12
,
Jul 26
,
Jul 26
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by robliao@chromium.org
, May 8 2018