Most browsers will only render <NOSCRIPT> when the user has disabled client-side scripting.
| Syntax | <NOSCRIPT>...</NOSCRIPT> |
|---|---|
| Attribute Specifications | |
| Contents | Block-level elements, inline elements |
| Contained in | APPLET, BLOCKQUOTE, BODY, BUTTON, CENTER, DD, DEL, DIV, FIELDSET, FORM, IFRAME, INS, LI, MAP, NOFRAMES, NOSCRIPT, OBJECT, TD, TH |
The NOSCRIPT element provides alternate content for a client-side script that was not executed. A script will fail to execute if the browser does not support the scripting language or if the user has disabled client-side scripting. NOSCRIPT should follow the SCRIPT element for which it provides alternate content.
|
Most browsers will fail to render the contents of <NOSCRIPT> if the scripting language is not supported and the user has enabled client-side scripting. Most browsers will only render <NOSCRIPT> when the user has disabled client-side scripting. |
| Netscape Navigator 2.x supports JavaScript 1.0 but still renders all <NOSCRIPT> content. |
Since client-side scripts usually provide dynamic interactivity that cannot be replaced by static content, the NOSCRIPT element is generally not useful. Authors should try to use client-side scripts as optional enhancements that are not integral components of the Web page. In the case of form validation, any error checking done by the client-side script should be repeated by the CGI script or Java servlet that handles the submission at the server.