Add ability for a BubbleReference to update the BubbleUI.

components/bubble/bubble_controller.cc

Index: components/bubble/bubble_controller.cc
diff --git a/components/bubble/bubble_controller.cc b/components/bubble/bubble_controller.cc
index e32cd21716428aa0845c41c6a865a6c4ff0b1849..eebe6c61b2aee5b5e6cb0cd029e0e331127ceab1 100644
--- a/components/bubble/bubble_controller.cc
+++ b/components/bubble/bubble_controller.cc
@@ -24,6 +24,10 @@ bool BubbleController::CloseBubble(BubbleCloseReason reason) {
   return manager_->CloseBubble(this->AsWeakPtr(), reason);
 }
 
+bool BubbleController::UpdateBubbleUI() {
+  return manager_->UpdateBubbleUI(this->AsWeakPtr());

[groby-ooo-7-16, 2015/09/03 17:30:01]

Does this need to flow through the manager? Who usually calls this?

[hcarmona, 2015/09/03 18:05:53]

Going through the manager ensures that we stay on the UI thread.

[groby-ooo-7-16, 2015/09/03 19:13:58]

Do we _need_ to ensure that? And if we do, let's ensure it in the controller.
(Because _it_ should certainly stay on the same thread as well)

+}
+
 void BubbleController::Show() {
   DCHECK(!bubble_ui_);
   bubble_ui_ = delegate_->BuildBubbleUI();
@@ -47,3 +51,9 @@ bool BubbleController::ShouldClose(BubbleCloseReason reason) {
   }
   return false;
 }
+
+bool BubbleController::UpdateBubbleUIInternal() {

[groby-ooo-7-16, 2015/09/03 17:30:01]

I decidedly dislike "Internal" functions. If we don't need to route through the
manager, this can go.

If we do, I think this should stay UpdateBubbleUi, and the public function
should become "RequestBubbleUiUpdate()" 

[hcarmona, 2015/09/03 18:05:53]

Done.

+  if (!bubble_ui_)
+    return false;
+  return delegate_->UpdateBubbleUI(bubble_ui_.get());
+}