Separate handler initialization from page initialization

chrome/browser/ui/webui/options2/core_options_handler2.h

Index: chrome/browser/ui/webui/options2/core_options_handler2.h
diff --git a/chrome/browser/ui/webui/options2/core_options_handler2.h b/chrome/browser/ui/webui/options2/core_options_handler2.h
index 8849a6ab77ec3d0f88f162597fd4fb69cd2ddc08..1c33522199117cd9b5d541bf1723e28886a34f16 100644
--- a/chrome/browser/ui/webui/options2/core_options_handler2.h
+++ b/chrome/browser/ui/webui/options2/core_options_handler2.h
@@ -98,10 +98,13 @@ class CoreOptionsHandler : public OptionsPageUIHandler {
     TYPE_LIST,
   };
 
-  // Callback for the "coreOptionsInitialize" message.  This message will
-  // trigger the Initialize() method of all other handlers so that final
-  // setup can be performed before the page is shown.
-  void HandleInitialize(const ListValue* args);
+  // TODO document

[Dan Beam, 2012/04/10 04:38:43]

do it

[Tyler Breisacher (Chromium), 2012/04/10 17:43:28]

Did it.

+  void HandleInitializeHandlers(const ListValue* args);
+
+  // Callback for the "coreOptionsInitializePages" message. This calls the
+  // InitializePage() method of all other handlers, to pass data back to the
+  // JavaScript on the page so it can populate the UI.
+  void HandleInitializePages(const ListValue* args);
 
   // Callback for the "fetchPrefs" message. This message accepts the list of
   // preference names passed as the |args| parameter (ListValue). It passes