Session manager not remembering / restoring window size for minimized windows
Reported by
xaser...@hotmail.de,
Oct 22 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Steps to reproduce the problem: 1. Open multiple windows (optionally multiple tabs) 2. Maximize each window 3. Minimize one or more window to the taskbar (e.g. Win+D) 4. Restore one window and exit chrome (ctrl+shift+q) 5. Restart Chrome What is the expected behavior? All restored windows are in the maximized state that they were in when chrome was exited What went wrong? All minimized windows are not in a maximized state anymore, but in the "normal" mode. Did this work before? No Chrome version: 64.0.3246.0 Channel: stable OS Version: 10.0 Flash Version: - I'm not sure why this has persistent for so long. For me the "steps to reproduce" are an essential part of my everyday workflow and I run into this problems multiple times a day.
,
Oct 23 2017
,
Oct 26 2017
Unable to reproduce the issue on the reported chrome version stable 64.0.3246.0 and on the latest canary 64.0.3250.0 with the below mentioned steps using windows 10, Ubuntu 14.04 and Mac 10.12.6. with the below mentioned steps. 1. Opened multiple windows with 2-3 tabs on few of the windows(checked "start where you left" on exit in settings) 2. Maximized each window 3. Minimized around two window to the taskbar 4. Exited the chrome. 5. Restarted Chrome again. We observed the windows opened in a maximised state. Attaching the screen cast of the same. @Reporter: Could you please check the screen cast and let us know if we have missed any steps in reproducing the issue. Thanks!
,
Oct 26 2017
Strange, please try with chromium. See attached.
,
Oct 26 2017
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 26 2017
Was able to reproduce issue the same way as shown above on Canary 64.0.3250.0.
,
Oct 30 2017
Thanks for the reply. Able to reproduce the issue on Windows 7 & windows 10 using chrome stable-62.0.3202.75 & Canary-64.0.3250.0 as per C#0. Observed that the minimized windows are not relaunched to its original size (i.e maximized state). This is non regression issue observed from M50 builds to latest Canary.Hence marking it as Untriaged to get more inputs from dev. Please find the attached screencast for reference. Note: Unable to reproduce the issue on Mac 10.12.6 7 Ubuntu 14.04
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Nov 25
Same issue filed in FF for 12y now. In FF sourcecode the issue is related to the API used by the sessionrestore manager not exposing sufficient information on whether the window was maximized or normal state before minimizing. API just exposes Windowstate as "normal", "minimized", "maximized". Likely the same in Chrome. Requires additional variable to remember whether window used to be maximized or not. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by xaser...@hotmail.de
, Oct 22 2017