The WHATWG recommendation:
it's generally better to avoid using noscript, and to instead design
the script to change the page from being a scriptless page to a
scripted page on the fly,
is fine as it is, but changing the page after scripts load can potentially mean seeing the no-script content briefly (FOUC - Flash of Unscripted Content). Putting the message in a <noscript> tag avoids that. <if js is available>
...
<else>
...
<the closing tag i guess/>Either way, make sure you have something sensible to display for all scenarios, even if it's just an error page. Mysterious blank pages are not fun.
The most infuriating one is when the javascript deletes the entire page content to show an error message due to some exception. Doubly so when the failing functionality is only used for tracking or some other unwanted "feature".
> “One of the few traps of the web”
…for some large value of “few”
The author answered their own question. In even the best effort case, noscript is the fallback.
I'm not even sure what they expect the website maintainer to do for most of that list. If they knew themselves, they would have put it in the blog post. Is this instead a call to draft new w3c specs or revisions? What am I misunderstanding? For a site that has "hacktivism" in the domain name, whining like this is a bad look.