It's worth noting that "disabling JS" is not the only way to disable JS. Sometimes it can happen inadvertently: * Bug accidentally makes it into production, pr

It's worth noting that "disabling JS" is not the only way to disable JS. Sometimes it can happen inadvertently: * Bug accidentally makes it into production, preventing some crucial feature from working? JS just got disabled. * User is browsing your site with an old device that doesn't support a feature you make use of? That JS has been disabled. * CDN fails and your fallback mechanism isn't working like you thought it was? JS got disabled. Not saying these are common occurrences, but I've seen all of them happen.