Professional Documents
Culture Documents
Script FPR Anything To Be Good
Script FPR Anything To Be Good
Script FPR Anything To Be Good
com/document/371530842/Fields-Virology-6th-Ed-PDF-Tahir99-VRG
Search MDN
Change language
Table of contents
Attributes
Notes
Examples
Specifications
Browser compatibility
See also
Tag omission None, both the starting and ending tag are mandatory.
Any element that accepts metadata content, or any element that accepts
Permitted parents
phrasing content.
Permitted ARIA
No role permitted
roles
async
For classic scripts, if the async attribute is present, then the classic script will be
fetched in parallel to parsing and evaluated as soon as it is available.
For module scripts, if the async attribute is present then the scripts and all their
dependencies will be executed in the defer queue, therefore they will get fetched in
parallel to parsing and evaluated as soon as they are available.
See Browser compatibility for notes on browser support. See also Async scripts for
asm.js.
crossorigin
Normal script elements pass minimal information to the window.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, use this attribute. See CORS settings attributes
for a more descriptive explanation of its valid arguments.
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, but before firing DOMContentLoaded.
Scripts with the defer attribute will prevent the DOMContentLoaded event from firing
until the script has loaded and finished evaluating.
Warning: This attribute must not be used if the src attribute is absent (i.e. for inline
scripts), in this case it would have no effect.
The defer attribute has no effect on module scripts — they defer by default.
Scripts with the defer attribute will execute in the order in which they appear in the
document.
This attribute contains inline metadata that a user agent can use to verify that a fetched
resource has been delivered free of unexpected manipulation. See Subresource
Integrity.
nomodule
This Boolean attribute is set to indicate that the script should not be executed in
browsers that support ES2015 modules — in effect, this can be used to serve fallback
scripts to older browsers that do not support modular JavaScript code.
nonce
referrerpolicy
Indicates which referrer to send when fetching the script, or resources fetched by the
script:
Note: An empty string value ("") is both the default value, and a fallback value if
referrerpolicy is not supported. If referrerpolicy is not explicitly specified on
the <script> element, it will adopt a higher-level referrer policy, i.e. one set on the
whole document or domain. If a higher-level policy is not available, the empty string
is treated as being equivalent to strict-origin-when-cross-origin.
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.
type
This attribute indicates the type of script represented. The value of this attribute will
be in one of the following categories:
Omitted or a JavaScript MIME type: This indicates the script is JavaScript. The
HTML5 specification urges authors to omit the attribute rather than provide a
redundant MIME type. In earlier browsers, this identified the scripting language of
the embedded or imported (via the src attribute) code. JavaScript MIME types are
listed in the specification.
module: Causes the code to be treated as a JavaScript module. The processing of the
script contents is not affected by the charset and defer attributes. For information
on using module, see our JavaScript modules guide. Unlike classic scripts, module
scripts require the use of the CORS protocol for cross-origin fetching.
Any other value: The embedded content is treated as a data block which won't be
processed by the browser. Developers must use a valid MIME type that is not a
JavaScript MIME type to denote data blocks. The src attribute will be ignored.
Deprecated attributes
charset
If present, its value must be an ASCII case-insensitive match for "utf-8". It’s
unnecessary to specify the charset attribute, because documents must use UTF-8, and
the script element inherits its character encoding from the document.
language
Like the type attribute, this attribute identifies the scripting language in use. Unlike
the type attribute, however, this attribute’s possible values were never standardized.
The type attribute should be used instead.
Notes
Scripts without async , defer or type="module" attributes, as well as inline scripts, are
fetched and executed immediately, before the browser continues to parse the page.
The script should be served with the text/javascript MIME type, but browsers are lenient
and only block them if the script is served with an image type (image/*); a video type
(video/*); an audio (audio/*) type; or text/csv. If the script is blocked, an error is sent to
the element, if not a load event is sent.
Examples
Basic usage
These examples show how to import (an external) script using the <script> element.
<script src="javascript.js"></script>
And the following examples show how to put (an inline) script inside the <script> element.
<script>
alert("Hello World!");
</script>
Module fallback
Browsers that support the module value for the type attribute ignore any script with a
nomodule attribute. That enables you to use module scripts while also providing nomodule-
marked fallback scripts for non-supporting browsers.
You can also use the <script> element to embed data in HTML with server-side rendering
by specifying a valid non-JavaScript MIME type in the type attribute.
Specifications
Specification
Browser compatibility
Report problems with this compatibility data on GitHub
desktop mobile
Full
Full Full support
scrip
t support support1 1
1 2 footnot
e
Full Full Full Full Full Full Full Full Full Full Full Full
async suppor suppor suppor suppor suppor suppor suppor suppor supp suppor suppor suppor
t1 t12 t1 tYes tYes tYes tYes tYes ort4 tYes tYes tYes
Full
Full Full Full No Full suppor
crossor
igin suppor suppor suppor suppor suppor tYes
t30 t18 t13 tNo t12 footno
te
Full
defer supportYes
footnote
Full support3.5
Full support12
footnote
Full support10
footnote
Full supportYes
footnote
Full supportYes
Full supportYes
footnote
Full supportYes
footnote
Full supportYes
Full support4
footnote
Full supportYes
Full supportYes
footnote
Compa
tibility
Full Full Full No Full Full Full Full Full unknow Full Full
integrit
y suppo suppo suppo suppor suppor suppor suppor suppor suppo n; suppor support
rt45 rt17 rt43 tNo tYes t11.1 t45 t45 rt43 please t11.3 5.0
update
this.?
language
Full Full Full Full Full Full Full Full Full Full Full Full
Deprecate suppo suppo suppo suppor suppor suppor suppor suppor suppo support suppor support
dNon- rt1 rt12 rt1 tYes tYes tYes tYes tYes rt4 Yes tYes Yes
standard
nomodule
Full Full Full No Full Full Full Full Full Full Full Full
Experimen suppo suppo suppo suppor suppor suppor suppor suppor suppo support suppor support
tal rt61 rt16 rt60 tNo t48 t11 t61 t61 rt60 45 t11 8.0
Compa
tibility
Full Full Full No Full No Full Full Full unknow No Full
referrer
policy suppo suppo suppo suppor suppor suppor suppor suppor suppo n; suppor support
rt70 rt79 rt65 tNo tYes tNo t70 t70 rt65 please tNo 10.0
update
this.?
Full Full Full Full Full Full Full Full Full Full Full Full
src suppo suppo suppo suppor suppor suppor suppor suppor suppo support suppor support
rt1 rt12 rt1 tYes tYes tYes tYes tYes rt4 Yes tYes Yes
Full Full Full Full Full Full Full Full Full Full Full Full
text suppo suppo suppo suppor suppor suppor suppor suppor suppo support suppor support
rt1 rt12 rt1 tYes tYes tYes tYes tYes rt4 Yes tYes Yes
Full Full Full Full Full Full Full Full Full Full Full Full
type suppo suppo suppo suppor suppor suppor suppor suppor suppo support suppor support
rt1 rt12 rt1 tYes tYes tYes tYes tYes rt4 Yes tYes Yes
type.mod Full
ule suppo
rt61
footn
ote
Full support79
footnote
Full support48
Full support60 No supportNo
footnote
Full support10.1
footnote
Full support61
footnote
Full support61
footnote
Full support45
Full support60
footnote
Full support10.3
footnote
Full support8.0
footnote
Legend
Full support
Full support
No support
No support
Compatibility unknown
Compatibility unknown
Compatibility notes
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 Firefox. In Firefox 4, 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), set
async="false" on the scripts you want to maintain order.
Warning: Never call document.write() from an async script. In Firefox 3.6, calling
document.write() has an unpredictable effect. In Firefox 4, calling document.write()
from an async script has no effect (other than printing a warning to the error console).
See also
document.currentScript
Ryan Grove's <script> and <link> node event compatibility chart
Flavio Copes' article on loading JavaScript efficiently and explaining the differences between
async and defer
JavaScript modules guide
Edit on GitHub
Source on GitHub
Report a problem with this content on GitHub
Want to fix the problem yourself? See our Contribution guide.
Related Topics
1. <canvas>
2. <noscript>
3. <script>
4. HTML Elements
Web Technologies
Learn Web Development
About MDN
Feedback
About
MDN Web Docs Store
Contact Us
Firefox
MDN
MDN on Twitter
MDN on Github
Mozilla
Mozilla on Twitter
Mozilla on Instagram
© 2005-2021 Mozilla and individual contributors. Content is available under these licenses.
Terms
Privacy
Cookies