Ensure that cookies dialog is populated with new cookies on reload

chrome/browser/resources/options2/cookies_view.js

Index: chrome/browser/resources/options2/cookies_view.js
diff --git a/chrome/browser/resources/options2/cookies_view.js b/chrome/browser/resources/options2/cookies_view.js
index 2e04f4d0a8eaa3519ce33cdfed425748f6a32b59..c80b93feb062ab5377bb4750bcf645b0658f00ca 100644
--- a/chrome/browser/resources/options2/cookies_view.js
+++ b/chrome/browser/resources/options2/cookies_view.js
@@ -32,11 +32,11 @@ cr.define('options', function() {
     queryDelayTimerId_: 0,
 
     /**
-     * The most recent search query, or null if the query is empty.
-     * @type {?string}
+     * The most recent search query, empty string if the query is empty.
+     * @type {string}
      * @private
      */
-    lastQuery_: null,
+    lastQuery_: '',

[battre, 2012/08/08 18:00:59]

I did this change, such that this.searchCookie(); triggered in
handleVisibleChange_ does not issue a new
chrome.send('updateCookieSearchResults', [filter]); here.

Without this change, CookiesViewHandler::SendChildren was called twice for the
root node on page reload. Once due to chrome.send('reloadCookies'); and once due
to chrome.send('updateCookieSearchResults', [filter]);

 
     initializePage: function() {
       OptionsPage.prototype.initializePage.call(this);
@@ -106,6 +106,8 @@ cr.define('options', function() {
       // cookies dialog or the apps one.
       chrome.send('setViewContext', [this.isAppContext()]);
 
+      chrome.send('reloadCookies');
+
       if (!this.initialized_) {
         this.initialized_ = true;
         this.searchCookie();