New issue
Advanced search Search tips

Issue 884987 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 888218
Owner: ----
Closed: Sep 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

When restoring minimized windows, they no longer stay minimized.

Reported by mwich...@gmail.com, Sep 18

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome, create a few windows, minimize some.
2. Crash Chrome.
3. Open it again.
4. Click restore tabs.

What is the expected behavior?
The minimized windows stay minimized in the dock.

What went wrong?
All the windows appear unminimized.

Did this work before? Yes 68

Chrome version: 69.0.3497.92  Channel: n/a
OS Version: OS X 10.13.6
Flash Version:
 
Labels: Needs-Triage-M69 Needs-Bisect
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET Needs-Feedback
mwichary@ Thanks for the issue...

Unable to reproduce the issue on reported chrome 69.0.3497.92 using mac 10.13.6.
Steps:
-----
1. Launched reported chrome 
2. Opened multiple windows and  minimized some windows
As we are not seen any chrome crashes.

@Reporter: Can you verify this issue with fresh profile that is not having any extensions and apps or reset all the flags. Let us know whether issue still persists. Also provide crash id from >> chrome://crashes/

Thanks..!
Components: -UI UI>Browser>Sessions
Mergedinto: 888218
Status: Duplicate (was: Unconfirmed)
I didn’t mean to imply Chrome crashes when you minimize windows. 

The bug is: if Chrome happens to crash, and then the session gets restored, the previously minimized Chrome windows don’t stay minimized when restored, which would be expected. (You can actually see them animate out from the dock upon Chrome relaunch.)

This is a regression, this used to work well in version 68 and before.
Thanks for your feedback. I merged this report into  issue 888218  because it addresses nearly the same problem.

Sign in to add a comment