OLD | NEW |
| 1 <div id="pageData-name" class="pageData">Commands</div> |
| 2 |
1 <!-- BEGIN AUTHORED CONTENT --> | 3 <!-- BEGIN AUTHORED CONTENT --> |
| 4 |
2 <p> | 5 <p> |
3 The commands API allows you to add keyboard shortcuts that trigger actions in | 6 The commands API allows you to add keyboard shortcuts that trigger actions in |
4 your extension. An action can be opening the browser action or page action popup | 7 your extension. An action can be opening the browser action or page action popup |
5 or sending a command to the extension. | 8 or sending a command to the extension. |
6 </p> | 9 </p> |
7 | 10 |
8 <h2 id="manifest">Manifest</h2> | 11 <h2 id="manifest">Manifest</h2> |
9 <p> | 12 <p> |
10 In addition to the "experimental" permission you must declare the "commands" | 13 In addition to the "experimental" permission you must declare the "commands" |
11 permission in your extension's manifest to use this API and set manifest_version | 14 permission in your extension's manifest to use this API and set manifest_version |
(...skipping 57 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
69 }); | 72 }); |
70 </pre> | 73 </pre> |
71 | 74 |
72 <p>The '_execute_browser_action' and '_execute_page_action' commands are | 75 <p>The '_execute_browser_action' and '_execute_page_action' commands are |
73 reserved for the action of opening your extension's popups. They won't normally | 76 reserved for the action of opening your extension's popups. They won't normally |
74 generate events that you can handle. If you need to take action based on your | 77 generate events that you can handle. If you need to take action based on your |
75 popup opening, consider listening for an 'onDomReady' event inside your popup's | 78 popup opening, consider listening for an 'onDomReady' event inside your popup's |
76 code. | 79 code. |
77 </p> | 80 </p> |
78 <!-- END AUTHORED CONTENT --> | 81 <!-- END AUTHORED CONTENT --> |
OLD | NEW |