Make ToolbarActionsModel ignore calls to AddComponentAction() before initialization

chrome/browser/ui/toolbar/media_router_action_controller.cc

Index: chrome/browser/ui/toolbar/media_router_action_controller.cc
diff --git a/chrome/browser/ui/toolbar/media_router_action_controller.cc b/chrome/browser/ui/toolbar/media_router_action_controller.cc
index 722745255b949eb1d22bd56fda177439e377fe63..1fac119e976cd5eb2b1becfa43b678aa99a2fb0c 100644
--- a/chrome/browser/ui/toolbar/media_router_action_controller.cc
+++ b/chrome/browser/ui/toolbar/media_router_action_controller.cc
@@ -61,6 +61,9 @@ MediaRouterActionController::MediaRouterActionController(
 }
 
 void MediaRouterActionController::MaybeAddOrRemoveAction() {
+  if (!component_action_delegate_->ActionsInitialized())

[Devlin, 2016/10/25 22:12:13]

I'd have a slight preference to put this check in
ToolbarActionsModel::AddComponentAction().

[takumif, 2016/10/26 01:22:01]

Yeah, that would be simpler.

I thought about adding the check to RemoveComponentAction() as well, but I think
it doesn't need it because if the model isn't initialized, HasAction() wouldn't
return true, in which case Remove shouldn't be called anyways.

+    return;
+
   if (ShouldEnableAction()) {
     if (!component_action_delegate_->HasComponentAction(
             ComponentToolbarActionsFactory::kMediaRouterActionId))