Chrome window resizes/moves after going full screen.
Reported by
j.b.hou...@gmail.com,
Oct 29
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Open chrome window. 2. Snap to one half of display using windows key + arrow key, or by dragging to edge of display. Problem is most obvious when snapping to the half of a display that borders another display. 3. Open any website in full screen using F11, or by double clicking a video. 4. Close full screen by hitting F11 or the ESC key. 5. Notice that the chrome window has resized/moved: a few pixels of the window now spill over to the other monitor. What is the expected behavior? The window returns to the position and size it was before going full screen. What went wrong? The window moves and/or resizes slightly, causing the window to spill over to my secondary monitor (and some of the content to be obscured because my second monitor has lower vertical resolution). Attached: Screenshot of the window spilling over to the second monitor. I added a red line to indicate the border between my displays. In this case it looks like there's a 7-pixel spillover (not sure if the amount is consistent). Did this work before? N/A Chrome version: 70.0.3538.77 Channel: stable OS Version: 10.0 Flash Version: Environment: Windows 10 - version 1809 - build 17763.55 Chrome - Version 70.0.3538.77 (Official Build) (64-bit) 2 displays, side by side - main display 3440x1440; secondary display 1920x1080. Does this happen on other browsers? I was able to reproduce similar behavior on Firefox (63.0 (32-bit)), but not on Edge (44.17763.1.0). Internet Explorer (11) completely resizes the window when going full screen from a non-maximized window (much more extreme than Firefox or Chrome). Both Firefox and Internet Explorer have trouble properly dispalying YouTube videos full screen when the window is not maximized (video doesn't render near the edge of the display and the window taskbar stays visible on top of the player).
,
Oct 29
After some more experimentation: it seems that every time I open and close full screen, the window grows exactly 7 pixels to the left, right and bottom. Repeatedly opening and closing full screen eventually causes the window to grow way off screen, obscuring many elements of the UI. Notice that in the attached screenshot the bottom of the scrollbar is no longer visible. I also verified that the problem still occurs on a fresh profile (i.e. no extensions).
,
Nov 2
Unable to reproduce the issue on Win-10 using chrome reported version #70.0.3538.77 and latest canary #72.0.3599.0. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Opened chrome window. 2. Snapped to one half of display by dragging to edge of display. 3. Opened youtube.com in full screen using F11. 4. Closed full screen by hitting F11. 5. Observed that window returned to the position and size it was before going full screen as expected. reporter@ - Could you please check the issue on latest canary #72.0.3599.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Nov 3
From you video it looks like you're not snapping the window to one half of the display. The bug only repro's for me after using the Snap feature. I installed chrome canary and was still able to repro the issue on a fresh profile. I attached a video. Notice that the first time I open and close full screen, the window resizes to its original size. Then, after I use Snap, the window grows every time I open and close full screen.
,
Nov 3
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 13
This bug was introduced in windows 10 1809 and also affects latest firefox and chrome canary. Windows 10 Build 18272 (Insider build) also has the bug, so only quick fix right now is to rollback to Windows 1803 if you can.
,
Dec 23
The bug is still there. Google Chrome: 73.0.3648.0 (Official Build) canary (64-bit) (cohort: Clang-64) Revision: 52c31cf757640851f6cea917a581ba5b05d43636-refs/branch-heads/3648@{#1} OS: Windows 10 OS Build 17763.195
,
Dec 23
copy of the video reproduction on streamable for easier viewing https://streamable.com/4t7qs |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by krajshree@chromium.org
, Oct 29