Fixes component extension commands assignment on reload.

chrome/test/data/extensions/api_test/keybinding/component/background.js

Index: chrome/test/data/extensions/api_test/keybinding/component/background.js
diff --git a/chrome/test/data/extensions/api_test/keybinding/component/background.js b/chrome/test/data/extensions/api_test/keybinding/component/background.js
new file mode 100644
index 0000000000000000000000000000000000000000..73ed4cd106e1dd26afdfbb6e952cf903404b49d4
--- /dev/null
+++ b/chrome/test/data/extensions/api_test/keybinding/component/background.js
@@ -0,0 +1,11 @@
+// Copyright 2015 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.
+
+var platformBinding = /Mac/.test(navigator.platform) ? 'Command+Shift+5' :
+    'Ctrl+Shift+5';
+chrome.commands.getAll(function(commands) {
+  chrome.test.assertEq(1, commands.length);
+  chrome.test.assertEq(platformBinding, commands[0].shortcut);

[Mike Wittman, 2015/02/13 22:11:20]

Can you move the keybinding checks into C++ to match the other tests in
extension_keybinding_apitest.cc? If so, you may be able to reuse one of the
existing keybinding test extensions (e.g. keybindings/basics) rather than
introducing a new one.

[David Tseng, 2015/02/20 19:13:37]

Unfortunately, I can't reuse because component extensions require a "key"
attribute in their manifest. I guess I could always add it to basics, but it
seems nice to keep things separate. I guess I could name it basics_component to
be clearer? It also seems nice to exercise the entire commands codepath from js.

[Mike Wittman, 2015/02/20 19:21:11]

Sounds reasonable. I'm OK with the name as-is.

+  chrome.test.notifyPass();
+});