Implemented event-dispatching for button clicks.

chrome/browser/chromeos/login/screens/base_screen.h

Index: chrome/browser/chromeos/login/screens/base_screen.h
diff --git a/chrome/browser/chromeos/login/screens/base_screen.h b/chrome/browser/chromeos/login/screens/base_screen.h
index a9483929f94aef4023aae0e53fc10235acd4e7c4..1f015bcc30dbf420124c388b42c3d5c0dc85a221 100644
--- a/chrome/browser/chromeos/login/screens/base_screen.h
+++ b/chrome/browser/chromeos/login/screens/base_screen.h
@@ -80,7 +80,7 @@ class BaseScreen {
 
   // Called when button with |button_id| was pressed. Notification
   // about this event comes from the JS counterpart.
-  virtual void OnButtonPressed(const std::string& button_id);
+  virtual void OnButtonClicked(const std::string& button_id);

[dzhioev (left Google), 2014/11/27 12:08:51]

I propose to rename this method to something more general. For example,
"OnUserActed(action_id)". 

[Denis Kuznetsov (DE-MUC), 2014/11/27 13:51:41]

OnUserAction() seems better to me.

[ygorshenin1, 2014/11/27 14:11:13]

Done.

 
   // The method is called each time some key in screen context is updated by JS
   // side. Should be implemented in subclasses.