One of the few traps of the web is how the <noscript>
element doesn't provides the right behavior.
Definition: The <noscript> element provides alternate content when JavaScript is entirely toggled off or entirely unsupported.
Sources:
<script> (W3C gives Tcl as example, I'd more point to JScript and VBScript, both of which are thankfully gone)While the way to obtain the right behavior is to have a generic textual element being updated/deleted by your own script using the DOM APIs. You could also make the scripts so optional for you to not need to provide a failure message, but that's not the right method when the scripts are needed for actually using the webpage.
And should be noted that WHATWG HTML contains a similar recommendation to the latter method:
Thenoscriptelement is a blunt instrument. Sometimes, scripts might be enabled, but for some reason the page's script might fail. For this reason, it's generally better to avoid usingnoscript, and to instead design the script to change the page from being a scriptless page to a scripted page on the fly, […]
Because the problem is, JavaScript can fail to load in several ways. Here's a non-exhaustive list of cases:
I see most of the above on a regular basis, about multiple times per week to few times a month, and I tend to browse simple websites. And that's without counting the various ways scripts tend to fail at properly handling errors.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。