Place the spinner in the right corner of the controls window.

chrome/browser/chromeos/login/user_input.h

+// Copyright (c) 2010 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 CHROME_BROWSER_CHROMEOS_LOGIN_USER_INPUT_H_
+#define CHROME_BROWSER_CHROMEOS_LOGIN_USER_INPUT_H_
+
+#include "gfx/rect.h"
+
+namespace chromeos {
+
+// Interface that is used to manage the state of the user input controls.
+class UserInput {
+ public:
+  virtual ~UserInput() {}
+
+  // Enables/Disables the input controls.
+  virtual void EnableInputControls(bool enabled) = 0;
+
+  // Clears and focuses the controls.
+  virtual void ClearAndFocusControls() = 0;
+
+  // Clears and focuses the password field.
+  virtual void ClearAndFocusPassword() = 0;
+
+  // Returns bounds of the main input field in screen coordinats (e.g. these

[whywhat, 2010/12/13 07:57:35]

same nit about coordinats

[altimofeev, 2010/12/13 15:42:45]

Done.

+  // bounds could be used to choose positions for the error bubble).
+  virtual gfx::Rect GetMainInputScreenBounds() const = 0;
+
+  // Returns whether custom bounds for the throbber should be used. If yes then
+  // |bounds| contains custom bounds that should be used.
+  virtual bool UseCustomBoundsForThrobber(const gfx::Size& throbber,

[whywhat, 2010/12/13 07:57:35]

Could we change this method to smth like StartThrobber(ThrobberManager*)? Thus
each UserInput would choose where to put the throbber without exposing bounds to
the caller. Caller won't have to treat the return code of this method
differently then.

[altimofeev, 2010/12/13 15:42:45]

I went further and implemented class that exposes start/stop interface.

+                                          gfx::Rect* bounds) = 0;
+};
+
+}  // namespace chromeos
+
+#endif  // CHROME_BROWSER_CHROMEOS_LOGIN_USER_INPUT_H_