Thanks for the correction. My point remains that the "NoScript" extension doesn't do anything with those "noscript" blocks, so they're not shown to the user despite the user not executing JS on the site.

This is a bit of a PITA when one tries to make the site "work well" with JS both enabled and disabled; or provide _alternatives_ for when the user-agent isn't running JS.

Those work really well when the user-agent is blocking JS globally, but not for NoScript: broken behaviour everywhere.

IIRC the noscript extension had the option to parse <noscript> if you disable scripts.

But if you are doing progressive enhancement correctly you should not need any <noscript> so this becomes a moot issue.