Restore window size after accessbility keyboard hides.

ash/wm/workspace/workspace_layout_manager.cc

Index: ash/wm/workspace/workspace_layout_manager.cc
diff --git a/ash/wm/workspace/workspace_layout_manager.cc b/ash/wm/workspace/workspace_layout_manager.cc
index 71f4b969f7f61c6e531651528bdfb3c45a6512e4..12abfd19611592a4f0bc79cd6d157ceb1e393fca 100644
--- a/ash/wm/workspace/workspace_layout_manager.cc
+++ b/ash/wm/workspace/workspace_layout_manager.cc
@@ -143,15 +143,28 @@ void WorkspaceLayoutManager::OnKeyboardBoundsChanging(
   aura::Window *window = text_input_client->GetAttachedWindow();
   if (!window || !window_->Contains(window))
     return;
-  gfx::Rect window_bounds = ScreenUtil::ConvertRectToScreen(
-      window_,
-      window->GetTargetBounds());
-  gfx::Rect intersect = gfx::IntersectRects(window_bounds, new_bounds);
-  int shift = std::min(intersect.height(),
-                       window->bounds().y() - work_area_in_parent_.y());
-  if (shift > 0) {
-    gfx::Point origin(window->bounds().x(), window->bounds().y() - shift);
-    SetChildBounds(window, gfx::Rect(origin, window->bounds().size()));
+  aura::Window *toplevel_window = window->GetToplevelWindow();
+  wm::WindowState* toplevel_window_state = wm::GetWindowState(toplevel_window);
+  if (!new_bounds.IsEmpty()) {
+    // Store existing bounds to be restored before resizing for keyboard if it
+    // is not already stored.
+    if (!toplevel_window_state->HasRestoreBounds()) {

[flackr, 2014/08/14 19:17:58]

nit: no curlies { } for single line statement.

Note: I think it's probably okay to clobber the restore bounds if the keyboard
was previously not shown, just not to clobber if the keyboard changes size. The
window may have restore bounds if side snapped for example.

[Peter Wen, 2014/08/15 13:44:48]

Done.

It seems that workspace_layout_manager's onKeyboardBoundsChanging is only used
when the window is non-maximized, so it has no restore bounds. This check should
always pass the first time VK is shown (in non-maximized mode) and once the VK
is hidden the previous restore bounds are used and discarded in preparation for
next time VK is shown.

If the window is at any time snapped to the side or maximized, before or during
this process, then the maximized case takes over and this code is no longer
relevant.

The only unexpected case I found is if a window is maximized, then the
accessibility keyboard is used, the window resizes and resets correctly back to
maximized, but afterwards the original unmaximized size is lost. That is not a
result of the code here but of the code for the maximized case clobbering the
restore bounds. I think that is unavoidable unless we store a stack of restore
bounds anyways.

+      toplevel_window_state->SaveCurrentBoundsForRestore();
+    }
+
+    gfx::Rect window_bounds = ScreenUtil::ConvertRectToScreen(
+        window_,
+        window->GetTargetBounds());
+    gfx::Rect intersect = gfx::IntersectRects(window_bounds, new_bounds);
+    int shift = std::min(intersect.height(),
+                         window->bounds().y() - work_area_in_parent_.y());
+    if (shift > 0) {

[flackr, 2014/08/14 19:17:58]

Should we even set restore bounds if there is no change?

[Peter Wen, 2014/08/15 13:44:48]

Yes, as that way even if the focused input area does not overlap with the
keyboard, we still restore to the correct one. "shift" is only positive if the
focused area overlaps with the VK's half of the screen.

[flackr, 2014/08/20 15:02:14]

Alright, sounds fine. It should be fine either way since it only tries to
restore if the window has restore bounds.

+      gfx::Point origin(window->bounds().x(), window->bounds().y() - shift);
+      SetChildBounds(window, gfx::Rect(origin, window->bounds().size()));
+    }
+  } else if (toplevel_window_state->HasRestoreBounds()) {
+    // Keyboard hidden, restore original bounds if they exist.
+    toplevel_window_state->SetAndClearRestoreBounds();
   }
 }