cros: Allow pin keyboard to keep focus without popping up the pin keyboard.

ui/keyboard/keyboard_util.h

 // Copyright (c) 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef UI_KEYBOARD_KEYBOARD_UTIL_H_
 #define UI_KEYBOARD_KEYBOARD_UTIL_H_
 
 #include <string>
 
 // TODO(beng): replace with forward decl once RootWindow is renamed.
@@ skipping 47 matching lines @@
   // Request virtual keyboard be suppressed.
   KEYBOARD_STATE_DISABLED,
 };
 
 // Gets the calculated keyboard bounds from |root_bounds|. The keyboard height
 // is specified by |keyboard_height|. This should be only called when keyboard
 // is in FULL_WDITH mode.
 KEYBOARD_EXPORT gfx::Rect FullWidthKeyboardBoundsFromRootBounds(
     const gfx::Rect& root_bounds, int keyboard_height);
 
+// Blocks the keyboard from showing up. This should only be used for cases where
+// the focus needs to be passed around without poping up the keyboard. It needs
+// to be turned off when done with otherwise the keyboard will not pop up again.
+KEYBOARD_EXPORT void SetForceDisableVirtualKeyboardForWebUi(bool disable);

[xiyuan, 2016/11/09 18:06:32]

Why do we need to call out "webui" in the API? Can it be used for other
purposes?

Also, do we want to make a ScopedVirtualKeyboardDisabler helper class to ensure
the VK is re-enabled after caller is done with it?

[sammiequon, 2016/11/10 21:06:01]

I added the webui becuase this function is used exclusively for the lock screen
webui at the moment and hopefully will be replaced by a better solution in the
future. If something else uses this we can drop the webui; what do you think?
Added scoped helper class.

[xiyuan, 2016/11/10 21:48:35]

As an API, it should be generic. I would say drop "webui" unless this should
only be called for an webui. And I don't think we have this case here.

Also, it seems that we can use

keyboard::SetRequestedKeyboardState(keyboard::KEYBOARD_STATE_DISABLED)

to achieve similar goal and maybe not even need a new API.

What do you think?

[sammiequon, 2016/11/10 22:36:56]

Dropped. Using SetRequestedKeyboardState would only work for the normal keyboard
and not the accessibility keyboard since accessibility keyboard takes charge
over all other things, except this newly added one.

[xiyuan, 2016/11/10 22:40:58]

Acknowledged.

+
+// Return true if keyboard has been blocked from showing up for web ui purposes.
+KEYBOARD_EXPORT bool GetForceDisableVirtualKeyboardForWebUi();
+
 // Sets the state of the a11y onscreen keyboard.
 KEYBOARD_EXPORT void SetAccessibilityKeyboardEnabled(bool enabled);
 
 // Gets the state of the a11y onscreen keyboard.
 KEYBOARD_EXPORT bool GetAccessibilityKeyboardEnabled();
 
 // Sets the state of the hotrod onscreen keyboard.
 KEYBOARD_EXPORT void SetHotrodKeyboardEnabled(bool enabled);
 
 // Gets the state of the hotrod onscreen keyboard.
@@ skipping 87 matching lines @@
 
 // Gets the override content url.
 KEYBOARD_EXPORT const GURL& GetOverrideContentUrl();
 
 // Logs the keyboard control event as a UMA stat.
 void LogKeyboardControlEvent(KeyboardControlEvent event);
 
 }  // namespace keyboard
 
 #endif  // UI_KEYBOARD_KEYBOARD_UTIL_H_