HTML <noscript> Tag
The HTML <noscript> tag represents alternative content for browsers that don't support javascript or other scripting languages.
The <noscript> tag is used along with the <script> tag to provide content for those user agents that don't support scripting.
Syntax
The <noscript> tag is written as <noscript></noscript> with the content inserted between the start and end tags. The <noscript> tag is typically placed after the end tag of the <script> element.
Like this:
Examples
Basic tag usage
Here's an example of <noscript> tag usage.
Attributes
Attributes can be added to an HTML element to provide more information about how the element should appear or behave.
There are 3 kinds of attributes that you can add to your HTML tags: Element-specific, global, and event handler content attributes.
The <noscript> element accepts the following attributes.
Element-Specific Attributes
This table shows the attributes that are specific to the <noscript> tag/element.
| Attribute | Description |
|---|---|
| None |
Global Attributes
The following attributes are standard across all HTML5 elements. Therefore, you can use these attributes with the <noscript> tag , as well as with all other HTML tags.
- accesskey
- class
- contenteditable
- contextmenu
- dir
- draggable
- dropzone
- hidden
- id
- inert
- itemid
- itemprop
- itemref
- itemscope
- itemtype
- lang
- spellcheck
- style
- tabindex
- title
- translate
For a full explanation of these attributes, see HTML 5 global attributes.
Event Handler Content Attributes
Event handler content attributes enable you to invoke a script from within your HTML. The script is invoked when a certain "event" occurs. Each event handler content attribute deals with a different event.
Below are the standard HTML5 event handler content attributes.
Again, you can use any of these with the <noscript> element, as well as any other HTML5 element.
- onabort
- oncancel
- onblur
- oncanplay
- oncanplaythrough
- onchange
- onclick
- oncontextmenu
- ondblclick
- ondrag
- ondragend
- ondragenter
- ondragexit
- ondragleave
- ondragover
- ondragstart
- ondrop
- ondurationchange
- onemptied
- onended
- onerror
- onfocus
- onformchange
- onforminput
- oninput
- oninvalid
- onkeydown
- onkeypress
- onkeyup
- onload
- onloadeddata
- onloadedmetadata
- onloadstart
- onmousedown
- onmousemove
- onmouseout
- onmouseover
- onmouseup
- onmousewheel
- onpause
- onplay
- onplaying
- onprogress
- onratechange
- onreadystatechange
- onscroll
- onseeked
- onseeking
- onselect
- onshow
- onstalled
- onsubmit
- onsuspend
- ontimeupdate
- onvolumechange
- onwaiting
For a full explanation of these attributes, see HTML 5 event handler content attributes.
Differences Between HTML 4 & HTML 5
In HTML 4, the <noscript> tag can only be used within the <body>.
In HTML5, the <noscript> tag can be used within either the <body> or <head> elements (as long as there are no ancestor <noscript> elements).
To see more detail on the two versions see HTML5 <noscript> Tag and HTML4 <noscript> Tag. Also check out the links to the official specifications below.
Template
Here's a template for the <noscript> tag with all available attributes for the tag (based on HTML5). These are grouped into attribute types, each type separated by a space. In many cases, you will probably only need one or two (if any) attributes. Simply remove the attributes you don't need.
For more information on attributes for this tag, see HTML5 <noscript> Tag and HTML4 <noscript> Tag.
Tag Details
For more details about the <noscript> tag, see HTML5 <noscript> Tag and HTML4 <noscript> Tag.
Specifications
Here are the official specifications for the <noscript> element.
- HTML5 Specification (W3C)
- HTML Living Standard (WHATWG)
- Current W3C Draft (the next version that is currently being worked on)
- HTML 4 (W3C)
What's the Difference?
W3C creates "snapshot" specifications that don't change once defined. So the HTML5 specification won't change once it becomes an official recommendation. WHATWG on the other hand, develops a "living standard" that is updated on a regular basis. In general, you will probably find that the HTML living standard will be more closely aligned to the current W3C draft than to the HTML5 specification.