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

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

Issue 219213007: Remove .html extension from links (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 6 years, 7 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 <p> 1 <p>
2 See <a href="devtools.html">DevTools APIs summary</a> for 2 See <a href="devtools">DevTools APIs summary</a> for
3 general introduction to using Developer Tools APIs. 3 general introduction to using Developer Tools APIs.
4 </p> 4 </p>
5 5
6 <h2 id="overview">Overview</h2> 6 <h2 id="overview">Overview</h2>
7 7
8 <p> 8 <p>
9 Each extension panel and sidebar is displayed as a separate HTML page. All 9 Each extension panel and sidebar is displayed as a separate HTML page. All
10 extension pages displayed in the Developer Tools window have access to all 10 extension pages displayed in the Developer Tools window have access to all
11 modules in <code>chrome.devtools</code> API, as well as to 11 modules in <code>chrome.devtools</code> API, as well as to
12 <a href="extension.html">chrome.extension</a> API. Other extension APIs are not 12 <a href="extension">chrome.extension</a> API. Other extension APIs are not
13 available to the pages within Developer Tools window, but you may invoke them 13 available to the pages within Developer Tools window, but you may invoke them
14 by sending a request to the background page of your extension, similarly to how 14 by sending a request to the background page of your extension, similarly to how
15 it's done in the <a href="overview.html#contentScripts">content scripts</a>. 15 it's done in the <a href="overview#contentScripts">content scripts</a>.
16 </p><p> 16 </p><p>
17 You can use the <code>$(ref:devtools.panels.setOpenResourceHandler) 17 You can use the <code>$(ref:devtools.panels.setOpenResourceHandler)
18 </code> method to install a 18 </code> method to install a
19 callback function that handles user requests to open a resource (typically, 19 callback function that handles user requests to open a resource (typically,
20 a click on a resource link in the Developer Tools window). At most one of the 20 a click on a resource link in the Developer Tools window). At most one of the
21 installed handlers gets called; users can specify (using the Developer Tools 21 installed handlers gets called; users can specify (using the Developer Tools
22 Settings dialog) either the default behavior or an extension to handle resource 22 Settings dialog) either the default behavior or an extension to handle resource
23 open requests. If an extension calls <code>setOpenResourceHandler()</code> 23 open requests. If an extension calls <code>setOpenResourceHandler()</code>
24 multiple times, only the last handler is retained. 24 multiple times, only the last handler is retained.
25 </p> 25 </p>
(...skipping 23 matching lines...) Expand all
49 Developer Tools window: 49 Developer Tools window:
50 50
51 <img src="{{static}}/images/devtools-panels.png" 51 <img src="{{static}}/images/devtools-panels.png"
52 style="margin-left: 20px" 52 style="margin-left: 20px"
53 width="686" height="289" 53 width="686" height="289"
54 alt="Extension icon panel on DevTools toolbar" /> 54 alt="Extension icon panel on DevTools toolbar" />
55 </p> 55 </p>
56 56
57 <p> 57 <p>
58 You can find examples that use this API in 58 You can find examples that use this API in
59 <a href="samples.html#chrome-query">Samples</a>. 59 <a href="samples#chrome-query">Samples</a>.
60 </p> 60 </p>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698