chrome/common/extensions/docs/server2/templates/intros/experimental_commands.html - Issue 10832042: Extensions Docs Server: Doc conversion script

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

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

Issue 10832042: Extensions Docs Server: Doc conversion script (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: everything but svn stuff Created 8 years, 4 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 | Annotate | Revision Log

« chrome/common/extensions/docs/server2/intro_data_source.py ('K') | « chrome/common/extensions/docs/server2/templates/intros/experimental_app.html ('k') | chrome/common/extensions/docs/server2/templates/intros/experimental_devtools_audits.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 <p>	1 <p>

2 The commands API allows you to add keyboard shortcuts that trigger actions in	2 The commands API allows you to add keyboard shortcuts that trigger actions in

3 your extension. An action can be opening the browser action or page action popup	3 your extension. An action can be opening the browser action or page action popup

4 or sending a command to the extension.	4 or sending a command to the extension.

5 </p>	5 </p>

6	6

7 <h2 id="manifest">Manifest</h2>	7 <h2 id="manifest">Manifest</h2>

8 <p>	8 <p>

9 In addition to the "experimental" permission you must declare the "commands"	9 In addition to the "experimental" permission you must declare the "commands"

10 permission in your extension's manifest to use this API and set manifest_version	10 permission in your extension's manifest to use this API and set manifest_version

(...skipping 55 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
66 chrome.experimental.commands.onCommand.addListener(function(command) {	66 chrome.experimental.commands.onCommand.addListener(function(command) {

67 console.log('Command:', command);	67 console.log('Command:', command);

68 });	68 });

69 </pre>	69 </pre>

70	70

71 <p>The '_execute_browser_action' and '_execute_page_action' commands are	71 <p>The '_execute_browser_action' and '_execute_page_action' commands are

72 reserved for the action of opening your extension's popups. They won't normally	72 reserved for the action of opening your extension's popups. They won't normally

73 generate events that you can handle. If you need to take action based on your	73 generate events that you can handle. If you need to take action based on your

74 popup opening, consider listening for an 'onDomReady' event inside your popup's	74 popup opening, consider listening for an 'onDomReady' event inside your popup's

75 code.	75 code.

76 </p>	76 </p>

OLD	NEW