New issue
Advanced search Search tips

Issue 878804 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Maximized window become unmaximized and lose original size when display scale factor changes

Reported by alvinhoc...@gmail.com, Aug 29

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.57 Safari/537.36

Steps to reproduce the problem:
1. Keep note of unmaximized Chrome window size, then maximize the Chrome window
2. Open display settings
3. Change scale factor of a monitor, or disable any monitor / unplug a monitor / close laptop lid (the two monitors should have different scale factor), i.e. actions that will cause the Chrome window to end up on a monitor with a different scale factor

What is the expected behavior?
The Chrome window is still maximized, and unmaximizing it will revert to about the same logical (scaled by display scale factor) size.

What went wrong?
The Chrome window become unmaximized while keeping the maximized size, thus losing the original unmaximized size info.

Did this work before? No 

Chrome version: 69.0.3497.57  Channel: beta
OS Version: 10.0
Flash Version: 

(Most) other applications doesn't show this behaviour. E.g. if you maximize a Windows Explorer window and fiddle with the display settings, it will still remain maximized and it retains its original unmaximized size.
 
Labels: Needs-Triage-M69
Cc: jbanavatu@chromium.org
Labels: Hotlist-DesktopUIChecked Target-70 Target-71 Target-72 M-72 Hotlist-DesktopUIValid FoundIn-70 FoundIn-72 FoundIn-71
Status: Untriaged (was: Unconfirmed)
**UI mass Triage**

Able to reproduce the issue on Windows 10 using chrome reported version-69.0.3497.57 S & latest Canary-72.0.3611 as per steps mentioned in C#0.

Observed maximized window remains unmaximized while keeping the maximized size,thus losing the original unmaximized size info from M60 builds to latest Canary. It is non regression issue, hence marking this issue as untriaged to get this addressed by dev team.

Thanks..!

Sign in to add a comment