--- title: tabs.executeScript() slug: Mozilla/Add-ons/WebExtensions/API/tabs/executeScript tags: - Chrome Extensions - Extensions - Plugins - WebExtensions - executeScript - tabs.executeScript() translation_of: Mozilla/Add-ons/WebExtensions/API/tabs/executeScript ---
将 JavaScript 代码注入页面。
You can inject code into pages whose URL can be expressed using a match pattern: meaning, its scheme must be one of "http", "https", "file", "ftp". To do this you must have the permission for the page's URL, either explicitly as a host permission, or via the activeTab permission.
You can also inject code into pages packaged with your own extension:
browser.tabs.create({url: "/my-page.html"}).then(() => { browser.tabs.executeScript({ code: `console.log('location:', window.location.href);` }); });
You don't need any special permissions to do this.
You can't inject code into any of the browser's built-in pages, such as about:debugging, about:addons, or the page that opens when you open a new empty tab.
The scripts you inject are called content scripts. Learn more about content scripts.
This is an asynchronous function that returns a Promise
.
var executing = browser.tabs.executeScript( tabId, // optional integer details // object )
tabId
{{optional_inline}}integer
. The ID of the tab in which to run the script. Defaults to the active tab of the current window.details
allFrames
{{optional_inline}}boolean
. If true
, the code will be injected into all frames of the current page. If true
and frameId
is set, then it will raise an error, frameId and allFrames are mutually exclusive. If it is false
, code is only injected into the top frame. Defaults to false
.code
{{optional_inline}}string
. Code to inject, as a text string. Warning: Don’t use this property to interpolate untrusted data into JavaScript, as this could lead to a security issue.file
{{optional_inline}}string
. Path to a file containing the code to inject. In Firefox, relative URLs not starting at the extension root are resolved relative to the current page URL. In Chrome, these URLs are resolved relative to the extension's base URL. To work cross-browser, you can specify the path as a relative URL, starting at the extension's root, like this: "/path/to/script.js"
.frameId
{{optional_inline}}integer
. The frame where the code should be injected. Defaults to 0
(the top-level frame).matchAboutBlank
{{optional_inline}}boolean
. If true
, the code will be injected into embedded "about:blank" and "about:srcdoc" frames if your extension has access to their parent document. The code cannot be inserted in top-level about: frames. Defaults to false
.runAt
{{optional_inline}}A Promise
that will be fulfilled with an array of objects, representing the result of the script in every injected frame.
The result of the script is the last evaluated statement, which is similar to what would be output (the results, not any console.log()
output) if you executed the script in the Web Console. For example, consider a script like this:
var foo='my result';foo;
Here the results array will contain the the string "my result
" as an element. The result values must be structured clonable.
If any error occurs the promise will be rejected with an error message.
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
{{Compat("webextensions.api.tabs.executeScript")}}
This example executes a one-line code snippet in the currently active tab:
function onExecuted(result) { console.log(`We made it green`); } function onError(error) { console.log(`Error: ${error}`); } var makeItGreen = 'document.body.style.border = "5px solid green"'; var executing = browser.tabs.executeScript({ code: makeItGreen }); executing.then(onExecuted, onError);
This example executes a script from a file, packaged with the extension, called "content-script.js". The script is executed in the currently active tab. The script is executed in subframes as well as the main document:
function onExecuted(result) { console.log(`We executed in all subframes`); } function onError(error) { console.log(`Error: ${error}`); } var executing = browser.tabs.executeScript({ file: "/content-script.js", allFrames: true }); executing.then(onExecuted, onError);
This example executes a script from a file, packaged with the extension, called "content-script.js". The script is executed in the tab with an ID of 2:
function onExecuted(result) { console.log(`We executed in tab 2`); } function onError(error) { console.log(`Error: ${error}`); } var executing = browser.tabs.executeScript( 2, { file: "/content-script.js" }); executing.then(onExecuted, onError);
{{WebExtExamples}}
This API is based on Chromium's chrome.tabs
API. This documentation is derived from tabs.json
in the Chromium code.
// Copyright 2015 The Chromium Authors. All rights reserved. // // Redistribution and use in source and binary forms, with or without // modification, are permitted provided that the following conditions are // met: // // * Redistributions of source code must retain the above copyright // notice, this list of conditions and the following disclaimer. // * Redistributions in binary form must reproduce the above // copyright notice, this list of conditions and the following disclaimer // in the documentation and/or other materials provided with the // distribution. // * Neither the name of Google Inc. nor the names of its // contributors may be used to endorse or promote products derived from // this software without specific prior written permission. // // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.