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

Unified Diff: chrome/common/extensions/docs/server2/templates/intros/devtools_inspectedWindow.html

Issue 10832042: Extensions Docs Server: Doc conversion script (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: script/build.py fixes Created 8 years, 5 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 side-by-side diff with in-line comments
Download patch
Index: chrome/common/extensions/docs/server2/templates/intros/devtools_inspectedWindow.html
diff --git a/chrome/common/extensions/docs/server2/templates/intros/devtools_inspectedWindow.html b/chrome/common/extensions/docs/server2/templates/intros/devtools_inspectedWindow.html
index 69741a474da890eec3b060041dcce9bb16325a97..98da740aeb8e705e1893f023f3fc3f270a80f9bc 100644
--- a/chrome/common/extensions/docs/server2/templates/intros/devtools_inspectedWindow.html
+++ b/chrome/common/extensions/docs/server2/templates/intros/devtools_inspectedWindow.html
@@ -1,3 +1,5 @@
+<div id="pageData-name" class="pageData"
+>chrome.devtools.inspectedWindow.* APIs</div>
<p>
Use <code>chrome.devtools.inspectedWindow</code>
to interact with the inspected window:
@@ -9,7 +11,6 @@ or obtain the list of resources within the page.
See <a href="devtools.html">DevTools APIs summary</a> for
general introduction to using Developer Tools APIs.
</p>
-
<h2>Overview</h2>
<p>
The <a href="#property-tabId"><code>tabId</code></a> property
@@ -48,7 +49,6 @@ The evaluated code may return a value that is passed to the extension callback.
The returned value has to be a valid JSON object (it may contain only
primitive JavaScript types and acyclic references to other JSON
objects).
-
<em>Please observe extra care while processing the data received from the
inspected page &mdash; the execution context is essentially controlled by the
inspected page; a malicious page may affect the data being returned to the
@@ -74,11 +74,9 @@ etc) within the inspected page. The <code>getContent()</code> and <code
<code>onResourceContentCommitted</code> event may be used to support
modification of the resource content, for example, by an external editor.
</p>
-
<h2 id="overview-examples">Examples</h2>
<p>The following code checks for the version of jQuery used by the inspected
page:
-
<pre>
chrome.devtools.inspectedWindow.eval(
"jQuery.fn.jquery",
@@ -90,8 +88,7 @@ chrome.devtools.inspectedWindow.eval(
}
);
</pre>
-
<p>
You can find more examples that use Developer Tools APIs in
<a href="samples.html#devtools">Samples</a>.
-</p>
+</p>

Powered by Google App Engine
This is Rietveld 408576698