Separate handler initialization from page initialization

chrome/browser/ui/webui/options2/options_ui2.cc

Index: chrome/browser/ui/webui/options2/options_ui2.cc
diff --git a/chrome/browser/ui/webui/options2/options_ui2.cc b/chrome/browser/ui/webui/options2/options_ui2.cc
index 50b39003a501954062d9667c53d958b3404f6ae2..2cee7f0d454eca59bd8f22fe49ea066de2f87b5d 100644
--- a/chrome/browser/ui/webui/options2/options_ui2.cc
+++ b/chrome/browser/ui/webui/options2/options_ui2.cc
@@ -376,15 +376,16 @@ void OptionsUI::InitializeHandlers() {
       handlers_[i]->InitializeHandler();
     initialized_handlers_ = true;
   }

[Dan Beam, 2012/04/05 17:58:35]

nit: \n

+#if defined(OS_CHROMEOS)
+  pointer_device_observer_->Init();
+#endif
+}
 
+void OptionsUI::InitializePages() {
   // Always initialize the page as when handlers are left over we still need to
   // do various things like show/hide sections and send data to the Javascript.
   for (size_t i = 0; i < handlers_.size(); ++i)
     handlers_[i]->InitializePage();
-
-#if defined(OS_CHROMEOS)
-  pointer_device_observer_->Init();
-#endif
 }
 
 void OptionsUI::AddOptionsPageUIHandler(DictionaryValue* localized_strings,