Issue metadata
Sign in to add a comment
|
Regression:Unable to restore browser window after adding a new person
Reported by
vineetha...@etouch.net,
Nov 20
|
||||||||||||||||||||
Issue descriptionChrome Version : 71.0.3578.62 (Official Build) Revision b1fa6dee27746dd62414ffad95ea3a7acf51ef16-refs/branch-heads/3578@{#760} 32/64-bit OS : Windows 10 What steps will reproduce the problem? 1. Launch chrome, maximize the browser window, press F11 to enter browser full screen mode. 2. Press 'Ctrl + Shift + M' and click on 'Manage people'. 3. Add a new person. 4. Now click on browser's maximize button for the new person and then click on restore down button. 5. Repeat step 4 and observe. Actual Result : Unable to restore browser window after adding a new person. Expected Result : Should be able to restore browser window even after adding a new person. This is a regression issue, broken in M-70 and providing the bisect using chromium-bisect script: Good Build : 69.0.3497.0 (Revision : 576754) Bad Build : 70.0.3498.0 (Revision : 577006) CHANGE-LOG URL: https://chromium.googlesource.com/chromium/src/+log/4cfc7169b72855a2a34ce3e24db42dc331d6ac13..5a7b19387769f3ffffad229635a95482b500ed49?pretty=fuller&n=10000 Suspect : r576873 ? @lgrey: 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. This is Win-10 specific issue and it can not be reproduced on Win(7,8,8.1), Linux(14.04 LTS) and Mac(10.13.1, 10.13.6, 10.14.2) OS. 2. Tried per revision bisect on Windows OS but unable to perform the same since getting "RuntimeError: We don't have enough builds to bisect" error, hence, providing chromium bisect. 3. Issue is also observed in Canary build #72.0.3616.0
,
Nov 20
Er, really +pbos@ this time
,
Nov 20
Looks doubtful to me and the changelog link is busted (it contains about 10-20 entries maybe, diff between the versions stated should be about 250? Diffs between the revisions shown: https://chromium.googlesource.com/chromium/src/+log/62da7b8c83c71af4aa669de4683c1a8de7faa8fc..69cde5da04c60170cd173dc32e6c6a57481086d2?pretty=fuller&n=10000 bsep@ any suspects?
,
Nov 21
I dunno, that's too many suspects to go through. It doesn't reproduce for me, anyway.
,
Nov 26
,
Nov 27
Update w.r.t. comment #5: Rechecked the above issue on Win 10 OS using latest available Canary build #72.0.3622.0 and observed that the issue is reproducible. Kindly refer the attached screen cast. Thank you
,
Nov 27
robliao@ can you triage this to someone who understands Windows? Happy to take it back if it turns out it was caused by my change.
,
Nov 29
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by lgrey@chromium.org
, Nov 20