New issue
Advanced search Search tips

Issue 883459 link

Starred by 1 user
Status: Closed
Owner:
andrewxu@chromium.org
Closed: Oct 15
Cc:
dgreid@chromium.org
afakhry@chromium.org
ovanieva@google.com
osh...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 776448



Sign in to add a comment

hitting full-screen (F4) twice doesn't return a snapped window to its previous position

Project Member Reported by afakhry@chromium.org, Sep 12 
Feedback: https://listnr.corp.google.com/product/208/reports?searchText=reportId:85644588927&filter=0&dateRange=Custom&startTimeMs=1536217200000&endTimeMs=1536735600000

hitting full-screen (F4) twice doesn't return the window to its previous position. It started docked to the right of the screen, after going full screen and back it's in the inconvenient location shown in the screenshot.

Comment 1 by andrewxu@chromium.org, Oct 12

Cc: afakhry@chromium.org
The reason is that Window Snapping does not change the Window's restore bounds. I am not sure whether it is actually what we want. Because in WindowStateTest.RestoreBounds (https://cs.chromium.org/chromium/src/ash/wm/window_state_unittest.cc?q=window_state_unittest&sq=package:chromium&g=0&l=335), it seems to be expected that Window's restore bounds are not affected by Window Snapping.

Comment 2 by osh...@chromium.org, Oct 13 

This is currently WAI. Hitting F4 in fullscreen state means "restore to normal", not "restore to previous".

Comment 3 by andrewxu@chromium.org, Oct 15

Status: Closed (was: Assigned)
►

Sign in to add a comment