Continue bitmap fetching for notifications.

chrome/common/chrome_notification_types.h

Index: chrome/common/chrome_notification_types.h
diff --git a/chrome/common/chrome_notification_types.h b/chrome/common/chrome_notification_types.h
index 3c5a498a2ed121c03f64fdf865946c16313c21a4..41065df3335703dcea9b6ff6e230b42974aab281 100644
--- a/chrome/common/chrome_notification_types.h
+++ b/chrome/common/chrome_notification_types.h
@@ -702,6 +702,10 @@ enum NotificationType {
   // balloon host (the pointer is usable). No details are expected.
   NOTIFICATION_NOTIFY_BALLOON_DISCONNECTED,
 
+  // This notification is sent when an image is downloaded by a background
+  // process for the sake of notifications for an image.
+  NOTIFICATION_NOTIFY_BITMAP_FETCH_COMPLETE,

[dcheng, 2013/05/22 19:38:35]

Is it possible to make this change without adding a notification?

[Pete Williamson, 2013/05/23 16:47:29]

I will need to listen to this notification in the client code when I write it. 
I will definitely need some notification, let me know if you think it would be
wise to reuse an existing notification for this, but my suspicion is that would
be unwise.

[dcheng, 2013/05/23 19:32:25]

I would suggest using the delegate or observer pattern instead, like URLFetcher
does. As a whole, I believe we're trying our usage of notifications throughout
the code base where it makes sense.

+
   // Upgrade notifications ---------------------------------------------------
 
   // Sent when Chrome believes an update has been installed and available for