Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(572)

Side by Side Diff: chrome/common/extensions/docs/templates/intros/commands.html

Issue 12996003: Dynamically generate a heading for Extension Docs API pages (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Moving logic into availability_data_source Created 7 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 <table class="intro"> 1 <table class="intro">
2 <tr> 2 <tr>
3 <th scope="col"></th> 3 <th scope="col"></th>
4 <th scope="col"></th> 4 <th scope="col"></th>
5 </tr> 5 </tr>
6 <tr> 6 <tr>
7 <td><strong>Description:</strong></td>
8 <td>Use the commands API to add keyboard shortcuts
9 that trigger actions in your extension,
10 for example, an action to open the browser action
11 or send a command to the extension.</td>
12 </tr>
13 <tr>
14 <td><strong>Availability:</strong></td>
15 <td>Google Chrome 25</td>
16 </tr>
17 <tr>
18 <td><strong>Permissions:</strong></td> 7 <td><strong>Permissions:</strong></td>
19 <td>None</td> 8 <td>None</td>
20 </tr> 9 </tr>
21 </table> 10 </table>
22 11
23 <h2 id="manifest">Manifest</h2> 12 <h2 id="manifest">Manifest</h2>
24 <p> 13 <p>
25 You must set manifest_version to (at least) 2 to use this API. 14 You must set manifest_version to (at least) 2 to use this API.
26 </p> 15 </p>
27 16
(...skipping 48 matching lines...) Expand 10 before | Expand all | Expand 10 after
76 console.log('Command:', command); 65 console.log('Command:', command);
77 }); 66 });
78 </pre> 67 </pre>
79 68
80 <p>The '_execute_browser_action' and '_execute_page_action' commands are 69 <p>The '_execute_browser_action' and '_execute_page_action' commands are
81 reserved for the action of opening your extension's popups. They won't normally 70 reserved for the action of opening your extension's popups. They won't normally
82 generate events that you can handle. If you need to take action based on your 71 generate events that you can handle. If you need to take action based on your
83 popup opening, consider listening for an 'onDomReady' event inside your popup's 72 popup opening, consider listening for an 'onDomReady' event inside your popup's
84 code. 73 code.
85 </p> 74 </p>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698