noscript JS-Disabled Fallback

Resolves HTML noscript fallback and parser treatment from the HTML parser scripting flag. With scripting enabled contents are text; with scripting disabled contents are markup. XML parsing and full content-model validation are outside this tool.

Description

Noscript provides fallback content according to the HTML parser’s scripting flag.

Noscript provides fallback content according to the HTML parser’s scripting flag. Enabled scripting changes how its contents are parsed, rather than merely hiding ordinary markup.1

Resolves HTML noscript fallback and parser treatment from the HTML parser scripting flag. With scripting enabled contents are text; with scripting disabled contents are markup. XML parsing and full content-model validation are outside this tool.

When to use noscript JS-Disabled Fallback

Use this for the following task: Resolves HTML noscript fallback and parser treatment from the HTML parser scripting flag. With scripting enabled contents are text; with scripting disabled contents are markup. XML parsing and full content-model validation are outside this tool.

Prepare the parsed attribute values, element states or ordered local lists requested below. Keep attribute presence separate from value.

How to use noscript JS-Disabled Fallback and understand its results

  1. Prepare the parsed attribute values, element states or ordered local lists requested below. Keep attribute presence separate from value.
  2. Enter scriptingEnabled, context using the field table, then run the tool.
  3. Read fallbackEligible, contentsParsedAs, headContentRestricted. Interpret flags, units, ordering and placeholder values using the rules below.
  4. Review any reported issue or failed check, correct the supplied values when appropriate, and verify the result in its intended context.
Input fieldMeaningValue type and boundsRequirement
scriptingEnabledScripting EnabledbooleanRequired
contextContextstring; choose "head", "body"Required

Supply the scripting flag and head/body context. Flag restricted head content only for head context with scripting disabled.2

fallbackEligible = !scriptingEnabled; contentsParsedAs = enabled ? text : markup

This summarizes the declared operation. Units, indexing, inclusivity and exceptional cases are explained in the surrounding text.

Output fieldMeaningValue type
fallbackEligibleFallback Eligibleboolean
contentsParsedAsContents Parsed Asstring
headContentRestrictedHead Content Restrictedboolean
json
{
  "input": {
    "scriptingEnabled": false,
    "context": "body"
  },
  "output": {
    "fallbackEligible": true,
    "contentsParsedAs": "markup",
    "headContentRestricted": false
  }
}

Limitations and assumptions

XML parsing and full content-model conformance are excluded. The flag is a caller-supplied parser state, not a check of whether one script failed.

This evaluates supplied local information; it does not fetch a page or run a browser. Malformed requests produce input errors. A successfully evaluated request can still contain false flags, empty result lists or a result outside the supplied threshold; those outcomes have the meanings stated above.

Alternative or Complementary methods

Choose script defer/async Execution Order Table for this operation: Classifies execution scheduling of ordinary parser-inserted classic or module scripts. Async wins over defer; inline classic flags are ignored. This assumes scripting enabled and successful fetch/evaluation, without dynamic insertion or blocking attributes. For a complementary task, use Canvas Fallback Content Note for this operation: Determines canvas fallback in interactive visual media from caller-supplied canvas support and scripting state. Disabled scripting or disabled canvas support displays fallback. Printing/static media and accessibility subtree behavior are outside this profile.

Further background: HTML / accessibility reference: noscript JS-Disabled Fallback.

References

  1. HTML / accessibility reference: noscript JS-Disabled Fallback — WHATWG

  2. noscript JS-Disabled Fallback — tool.io

Similar or alternative tools

  • script defer/async Execution Order Table

    Classifies execution scheduling of ordinary parser-inserted classic or module scripts. Async wins over defer; inline classic flags are ignored. This assumes scripting enabled and successful fetch/evaluation, without dynamic insertion or blocking attributes.

  • Canvas Fallback Content Note

    Determines canvas fallback in interactive visual media from caller-supplied canvas support and scripting state. Disabled scripting or disabled canvas support displays fallback. Printing/static media and accessibility subtree behavior are outside this profile.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies