翻譯不完整。請協助 翻譯此英文文件。
Summary
HTML Script Element (<script>
) 是用來在 HTML 或 XHTML 文件嵌入或是引用程式碼。
沒有 async
或 defer
屬性的腳本(Scripts)以及內嵌腳本(Scripts)會在瀏覽器解析頁面前取出並立刻執行。
Content categories | Metadata content, Flow content, Phrasing content. |
---|---|
允許的內容 | 動態腳本,例如 application/javascript |
標籤不閉合 | None, both the starting and ending tag are mandatory. |
允許的父元素 | 任何可接受 metadata content 的元素或是任何接受 phrasing content 的元素 |
DOM interface | HTMLScriptElement |
Attributes
此元素包含了 全域屬性。
async
HTML5- Set this Boolean attribute to indicate that the browser should, if possible, execute the script asynchronously. It has no effect on inline scripts (i.e., scripts that don't have the src attribute).
- 關於其瀏覽器的支援程度可參考《Browser compatibility 》,另請參閱《 Async scripts for asm.js 》。
integrity
- Contains inline metadata that a user agent can use to verify that a fetched resource has been delivered free of unexpected manipulation. 請參閱《 Subresource Integrity 》。
src
- This attribute specifies the URI of an external script; this can be used as an alternative to embedding a script directly within a document. If a
script
element has asrc
attribute specified, it should not have a script embedded inside its tags. type
- This attribute identifies the scripting language of code embedded within a
script
element or referenced via the element’ssrc
attribute. This is specified as a MIME type; examples of supported MIME types includetext/javascript
,text/ecmascript
,application/javascript
, andapplication/ecmascript
. If this attribute is absent, the script is treated as JavaScript.
Note that in Firefox you can use advanced features such as let statements and other features in later JS versions, by usingtype=application/javascript;version=1.8
. Beware, however, that as this is a non-standard feature, this will most likely break support for other browsers, in particular Chromium-based browsers. - For how to include exotic programming languages, read about Rosetta.
text
- Like the
textContent
attribute, this attribute sets the text content of the element. Unlike thetextContent
attribute, however, this attribute is evaluated as executable code after the node is inserted into the DOM. language
- Like the
type
attribute, this attribute identifies the scripting language in use. Unlike thetype
attribute, however, this attribute’s possible values were never standardized. Thetype
attribute should be used instead. defer
- This Boolean attribute is set to indicate to a browser that the script is meant to be executed after the document has been parsed. Since this feature hasn't yet been implemented by all other major browsers, authors should not assume that the script’s execution will actually be deferred. The
defer
attribute shouldn't be used on scripts that don't have thesrc
attribute. Since Gecko 1.9.2, thedefer
attribute is ignored on scripts that don't have thesrc
attribute. However, in Gecko 1.9.1 even inline scripts are deferred if thedefer
attribute is set. crossorigin
- Normal
script
elements pass minimal information to thewindow.onerror
for scripts which do not pass the standard CORS checks. To allow error logging for sites which use a separate domain for static media, several browsers have enabled thecrossorigin
attribute for scripts using the same definition as the standard imgcrossorigin
attribute. Efforts to standardize this attribute are underway on the WHATWG mailing list.
範例
<!-- HTML4 and (x)HTML --> <script type="text/javascript" src="javascript.js"></script> <!-- HTML5 --> <script src="javascript.js"></script>
規格
Specification | Status | Comments |
---|---|---|
HTML5 The definition of '<script>' in that specification. |
Recommendation | |
HTML 4.01 Specification The definition of '<script>' in that specification. |
Recommendation | |
Subresource Integrity The definition of '<script>' in that specification. |
Working Draft | Adds the integrity attribute. |
瀏覽器支援度
Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari |
---|---|---|---|---|---|
Basic support | 1.0 | 1.0 (1.7 or earlier)[2] | (Yes) | (Yes) | (Yes) |
async attribute | (Yes)[1] | 3.6 (1.9.2)[1] | 10[1] | Not supported[1] | (Yes)[1] |
defer attribute | (Yes) | 3.5 (1.9.1) |
4[3] |
Not supported | (Yes) |
crossorigin attribute | 30.0 | 13 (13) | Not supported | 12.50 | (Yes)[4] |
integrity attribute | 45.0 | 43 (43) | Not supported[5] |
Feature | Android | Android Webview | Firefox Mobile (Gecko) | IE Mobile | Opera Mobile | Safari Mobile | Chrome for Android |
---|---|---|---|---|---|---|---|
Basic support | (Yes) | (Yes) | 1.0 (1.0)[2] | (Yes) | (Yes) | (Yes) | (Yes) |
async attribute | (Yes)[1] | (Yes)[1] | 1.0 (1.0)[1] | Not supported[1] | ?[1] | (Yes)[1] | (Yes)[1] |
defer attribute | (Yes) | (Yes) | 1.0 (1.0) | Not supported | ? | (Yes) | (Yes) |
integrity attribute | Not supported | 45.0 | 43 (43) | 45.0 |
[1] In older browsers that don't support the async
attribute, parser-inserted scripts block the parser; script-inserted scripts execute asynchronously in IE and WebKit, but synchronously in Opera and pre-4.0 Firefox. In Firefox 4.0, the async
DOM property defaults to true
for script-created scripts, so the default behavior matches the behavior of IE and WebKit. To request script-inserted external scripts be executed in the insertion order in browsers where the document.createElement("script").async
evaluates to true
(such as Firefox 4.0), set .async=false
on the scripts you want to maintain order. Never call document.write()
from an async
script. In Gecko 1.9.2, calling document.write()
has an unpredictable effect. In Gecko 2.0, calling document.write()
from an async
script has no effect (other than printing a warning to the error console).
[2] Starting in Gecko 2.0 (Firefox 4 / Thunderbird 3.3 / SeaMonkey 2.1), inserting script elements that have been created by calling document.createElement("script")
into the DOM no longer enforces execution in insertion order. This change lets Gecko properly abide by the HTML5 specification. To make script-inserted external scripts execute in their insertion order, set .async=false
on them.
Also, <script>
elements inside <iframe>
, <noembed>
and <noframes>
elements are now executed, for the same reasons.
[3] In versions prior to Internet Explorer 10 Trident implemented <script>
by a proprietary specification. Since version 10 it conforms to the W3C specification.
[4] The crossorigin
attribute was implemented in WebKit in WebKit bug 81438.
[5] WebKit bug 148363 tracks WebKit implementation of Subresource Integrity (which includes the integrity
attribute).