Fix missing entry showing number of cookies in first domain of chrome://settings/cookies

chrome/browser/resources/options2/cookies_list.js

Index: chrome/browser/resources/options2/cookies_list.js
diff --git a/chrome/browser/resources/options2/cookies_list.js b/chrome/browser/resources/options2/cookies_list.js
index 0968f3c4668bbd77772dfb173931cc2a7505b6c6..804597cd89159547afc9371f43c2f82811b08c40 100644
--- a/chrome/browser/resources/options2/cookies_list.js
+++ b/chrome/browser/resources/options2/cookies_list.js
@@ -597,7 +597,30 @@ cr.define('options', function() {
         // This allows the list items to be garbage collected when they scroll
         // out of view (except the expanded item, which we cache). This is
         // transparent except in the setter and getter, where we handle it.
-        this.parent_ = parent.listIndex;
+        if (this.parent_ == undefined || parent.listIndex != -1) {

[Mike Mammarella, 2012/08/14 00:50:56]

I'm not quite sure I understand the first part of this condition. Why not just
"if (parent.listIndex != -1) {" here? Is the idea that if we have no parent
right now, then the fake -1 index CookieListItem is OK, but otherwise we want to
ignore attempting to set it on top of the previous parent?

[battre, 2012/08/17 15:59:05]

This is actually necessary. This way the parent with an invalid index can be
registered once and update the link via the 'listIndexChange' event that we
subscribe to below. If we remove the first condition, no summaries are shown at
all.

+          // Setting the parent is somewhat tricky because the CookieListItem
+          // constructor has side-effects on the |origin| that it wraps. Every
+          // time a CookieListItem is created for an |origin|, it registers
+          // itself as the parent of the |origin|.
+          // The List implementation may create a temporary CookieListItem item
+          // that wraps the |origin| of the very first entry of the CokiesList,
+          // when the List is redrawn the first time. This temporary
+          // CookieListItem is fresh (has listIndex = -1) and is never inserted
+          // into the List. Therefore it gets never updated. This destroys the
+          // chain of parent pointers.
+          // This is the stack trace:
+          //     CookieListItem
+          //     CookiesList.createItem
+          //     List.measureItem
+          //     List.getDefaultItemSize_
+          //     List.getDefaultItemHeight_
+          //     List.getIndexForListOffset_
+          //     List.getItemsInViewPort
+          //     List.redraw
+          //     List.endBatchUpdates
+          //     CookiesList.loadChildren
+          this.parent_ = parent.listIndex;
+        }
         this.list_ = parent.list;
         parent.addEventListener('listIndexChange',
                                 this.parentIndexChanged_.bind(this));