Some improvement of validation message bubble UI.

chrome/renderer/validation_message_agent.h

Index: chrome/renderer/validation_message_agent.h
diff --git a/chrome/renderer/validation_message_agent.h b/chrome/renderer/validation_message_agent.h
index 7113b074a4a3ba04f0c068e14e82df3f8c98bc27..3c10fe16ce941470b90e89a753d5b32733e94d12 100644
--- a/chrome/renderer/validation_message_agent.h
+++ b/chrome/renderer/validation_message_agent.h
@@ -22,11 +22,14 @@ class ValidationMessageAgent : public content::RenderViewObserver,
 
  private:
   // WebValidationMessageClient functions:
-  virtual void showValidationMessage(const WebKit::WebRect& anchor_in_screen,
+  virtual void showValidationMessage(const WebKit::WebRect& anchor_in_root_view,
                                      const WebKit::WebString& main_text,
                                      const WebKit::WebString& sub_text,
                                      WebKit::WebTextDirection hint) OVERRIDE;
   virtual void hideValidationMessage() OVERRIDE;
+  // TOOD(tkent): add OVERRIDE before landing this.

[Nico, 2013/06/10 14:51:40]

do we add OVERRIDE for overriding blink methods? I once heard that we don't so
that changing these methods requires only 3-sided changes not 4-sided ones.

[tkent, 2013/06/11 07:02:43]

Yeah, OVERRIDE is optional in a case of implementing Blink API in Chromium
AFAIK.

+  virtual void moveValidationMessage(
+      const WebKit::WebRect& anchor_in_root_view);
 
   DISALLOW_COPY_AND_ASSIGN(ValidationMessageAgent);
 };