Docserver: Display API features that are available to content scripts

chrome/common/extensions/docs/templates/articles/content_scripts.html

 <h1>Content Scripts</h1>
 
 
 <p>
 Content scripts are JavaScript files that run in the context of web pages.
 By using the standard
 <a href="http://www.w3.org/TR/DOM-Level-2-HTML/">Document
 Object Model</a> (DOM),
 they can read details of the web pages the browser visits,
 or make changes to them.
 </p>
 
 <p>
 Here are some examples of what content scripts can do:
 </p>
 
 <ul>
   <li>Find unlinked URLs in web pages and convert them into hyperlinks
   <li>Increase the font size to make text more legible
   <li>Find and process <a href="http://microformats.org/">microformat</a> data in the DOM
 </ul>
 
 <p>
 However, content scripts have some limitations.
 They <b>cannot</b>:
 </p>
 
 <ul>
   <li>
-    Use chrome.* APIs
-    (except for parts of
-    <a href="extension"><code>chrome.extension</code></a>)
+    Use chrome.* APIs, with the exception of:

[not at google - send to devlin, 2014/07/09 02:55:55]

this is really interesting. it's uncovered several bugs!

[ahernandez, 2014/07/09 19:22:36]

Are APIs available to content scripts that shouldn't be?

[not at google - send to devlin, 2014/07/09 20:49:53]

yup

+    <ul id="content_script_supported_nodes">
+      {{#api:features}}

[not at google - send to devlin, 2014/07/09 02:55:55]

"content_scripts" would be better than "features".

+      <li>
+        $(ref:{{api.name}})
+        {{^api.fullSupport}}
+          ({{#n:api.supportedNodes}}
+           $(ref:{{n.parent}}.{{n.node}} {{n.node}})
+           {{^n.last}},{{/n.last}}
+           {{/api.supportedNodes}})
+        {{/api.fullSupport}}
+      </li>
+      {{/features}}
+    </ul>
   </li>
   <li>
     Use variables or functions defined by their extension's pages
   </li>
   <li>
     Use variables or functions defined by web pages or by other content scripts
   </li>
 </ul>
 
 <p>
@@ skipping 423 matching lines @@
 
 <p>
 The next video describes message passing,
 featuring an example of a content script
 sending a request to its parent extension.
 </p>
 
 <div class="video-container">
   <iframe title="YouTube video player" width="640" height="390" src="//www.youtube.com/embed/B4M_a7xejYI?rel=0" frameborder="0" allowfullscreen></iframe>
 </div>