1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
// Copyright 2014 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
#include "chrome/browser/ui/toolbar/component_toolbar_actions_factory.h"
#include "base/lazy_instance.h"
#include "chrome/browser/ui/toolbar/toolbar_action_view_controller.h"
#include "extensions/common/feature_switch.h"
namespace {
ComponentToolbarActionsFactory* testing_factory_ = nullptr;
base::LazyInstance<ComponentToolbarActionsFactory> lazy_factory =
LAZY_INSTANCE_INITIALIZER;
} // namespace
ComponentToolbarActionsFactory::ComponentToolbarActionsFactory() {}
ComponentToolbarActionsFactory::~ComponentToolbarActionsFactory() {}
// static
ComponentToolbarActionsFactory* ComponentToolbarActionsFactory::GetInstance() {
return testing_factory_ ? testing_factory_ : &lazy_factory.Get();
}
ScopedVector<ToolbarActionViewController>
ComponentToolbarActionsFactory::GetComponentToolbarActions() {
ScopedVector<ToolbarActionViewController> component_actions;
// This is currently behind the extension-action-redesign flag, as it is
// designed for the new toolbar.
if (!extensions::FeatureSwitch::extension_action_redesign()->IsEnabled())
return component_actions.Pass();
// Add component toolbar actions here.
// This current design means that the ComponentToolbarActionsFactory is aware
// of all actions. Since we should *not* have an excessive amount of these
// (since each will have an action in the toolbar or overflow menu), this
// should be okay. If this changes, we should rethink this design to have,
// e.g., RegisterChromeAction().
return component_actions.Pass();
}
// static
void ComponentToolbarActionsFactory::SetTestingFactory(
ComponentToolbarActionsFactory* factory) {
testing_factory_ = factory;
}
|
