Whitelist virtual keyboard container to process events at login screen

ash/shell_window_ids.h

 // Copyright (c) 2012 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 ASH_SHELL_WINDOW_IDS_H_
 #define ASH_SHELL_WINDOW_IDS_H_
 
 // Declarations of ids of special shell windows.
 
 namespace ash {
@@ skipping 84 matching lines @@
 // The container for special components overlaid onscreen, such as the
 // region selector for partial screenshots.
 const int kShellWindowId_OverlayContainer = 21;
 
 // ID of the window created by PhantomWindowController or DragWindowController.
 const int kShellWindowId_PhantomWindow = 22;
 
 // The topmost container, used for power off animation.
 const int kShellWindowId_PowerButtonAnimationContainer = 23;
 
+// The virtual keyboard container.
+const int kShellWindowId_VirtualKeyboardContainer = 24;

[James Cook, 2013/08/08 17:29:44]

Where does this container actually sit in the hierarchy of containers?  Unless
it is actually on top of the power button animation container, this line should
go in the middle of the file somewhere and the IDs all adjusted.

[bshe, 2013/08/08 19:39:24]

I am sure what's the rule to order the IDs. Keyboard container is a direct
children of root_window (the same level as DesktopBackgroundContainer). My best
guess is to put it under it but I could be wrong. Do you have suggestion?

On 2013/08/08 17:29:44, James Cook wrote:

[James Cook, 2013/08/08 19:52:39]

This seems fine.

+
 }  // namespace internal
 
 }  // namespace ash
 
 
 #endif  // ASH_SHELL_WINDOW_IDS_H_