Fix the issue of cursor being shown at startup.

chrome/browser/ui/ash/ash_init.cc

Index: chrome/browser/ui/ash/ash_init.cc
diff --git a/chrome/browser/ui/ash/ash_init.cc b/chrome/browser/ui/ash/ash_init.cc
index d45a93ce5ee8fc8642bd079e08c868586da886a8..337e8a94fe065dbd61281d51fed71ed55df33ad4 100644
--- a/chrome/browser/ui/ash/ash_init.cc
+++ b/chrome/browser/ui/ash/ash_init.cc
@@ -55,16 +55,14 @@ void OpenAsh() {
     // Aura window is closed.
     ui::HideHostCursor();
   }
+
+  // Hide the mouse cursor completely at boot.
+  if (!chromeos::UserManager::Get()->IsUserLoggedIn())
+    ash::Shell::set_initially_hide_cursor(true);

[Daniel Erat, 2012/10/31 13:18:53]

Just to double-check, is it still shown as soon as the user moves the mouse?

I'm not sure that this is the right behavior.  I think that most developers run
local builds in non-logged-in mode; it might be strange if the cursor is always
hidden when they do that.  I think we really only want to hide it when we're
displaying the login screen or OOBE.

[mazda, 2012/11/20 03:30:20]

Yes, CompoundEventFilter::SetCursorVisibilityOnEvent will show the cursor as
soon as the user moves the mouse.
That's a good point. I changed the code to hide cursor only when displaying the
login screen if developer runs local builds on desktop.

 #endif
 
-  if (use_fullscreen) {
+  if (use_fullscreen)
     aura::DisplayManager::set_use_fullscreen_host_window(true);
-#if defined(OS_CHROMEOS)
-    // Hide the mouse cursor completely at boot.
-    if (!chromeos::UserManager::Get()->IsUserLoggedIn())
-      ash::Shell::set_initially_hide_cursor(true);
-#endif
-  }
 
   // Its easier to mark all windows as persisting and exclude the ones we care
   // about (browser windows), rather than explicitly excluding certain windows.