Chromium Code Reviews| Index: chrome/common/extensions/docs/templates/articles/content_scripts.html |
| diff --git a/chrome/common/extensions/docs/templates/articles/content_scripts.html b/chrome/common/extensions/docs/templates/articles/content_scripts.html |
| index eca015edee7e9ed576ef9c6f1aef0da8026f70f7..daa6acbbafd418a581b0e0e905c0709bd811bad5 100644 |
| --- a/chrome/common/extensions/docs/templates/articles/content_scripts.html |
| +++ b/chrome/common/extensions/docs/templates/articles/content_scripts.html |
| @@ -27,9 +27,20 @@ They <b>cannot</b>: |
| <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
ahernandez
2014/07/09 19:22:36
Are APIs available to content scripts that shouldn
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 |