summaryrefslogtreecommitdiffstats
path: root/chrome/common/extensions/docs/content_scripts.html
diff options
context:
space:
mode:
authoraa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-11-25 02:05:39 +0000
committeraa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-11-25 02:05:39 +0000
commit719663e4f49853e2a9ff84bc0ac29cca484105d1 (patch)
tree175f6f17d37984d9fcea0698f28efece6d2195ef /chrome/common/extensions/docs/content_scripts.html
parent6776c72f56c29972bfd47efc1a1cf1629e3c7da2 (diff)
downloadchromium_src-719663e4f49853e2a9ff84bc0ac29cca484105d1.zip
chromium_src-719663e4f49853e2a9ff84bc0ac29cca484105d1.tar.gz
chromium_src-719663e4f49853e2a9ff84bc0ac29cca484105d1.tar.bz2
Introduce a new 'all_frames' property to content scripts and
default it to false. This should improve performance in sites that use frames and elimiate confusion, since in most cases developers *don't* expect content scripts to match frames. Review URL: http://codereview.chromium.org/412008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33035 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/extensions/docs/content_scripts.html')
-rw-r--r--chrome/common/extensions/docs/content_scripts.html8
1 files changed, 8 insertions, 0 deletions
diff --git a/chrome/common/extensions/docs/content_scripts.html b/chrome/common/extensions/docs/content_scripts.html
index 20a6196..f975bc4 100644
--- a/chrome/common/extensions/docs/content_scripts.html
+++ b/chrome/common/extensions/docs/content_scripts.html
@@ -400,6 +400,14 @@ learn about the
<b>NOTE:</b> In <code>document_idle</code>, content scripts may not necessarily receive the window.onload event, because they may run after it has
already fired. In most cases, listening for the onload event is unnecessary for content scripts running at <code>document_idle</code> because they are guaranteed to run after the DOM is complete. If your script definitely needs to run after <code>window.onload</code> you can check if it has already fired by using the <code><a href="http://www.whatwg.org/specs/web-apps/current-work/#dom-document-readystate">document.readyState</a></code> property.</td>
</tr>
+ <tr>
+ <td>all_frames</td>
+ <td>boolean</td>
+ <td><em>Optional.</em>
+ Controls whether the content script runs in all frames of the matching page, or only the top frame.
+ <br><br>
+ Defaults to <code>false</code>, meaning that only the top frame is matched.</td>
+ </tr>
</tbody></table>