#seckit-noscript-tag { display: none; }
and it works fine... (or you can remove the matching div from the web inspector if you are using a browser which has one).Aside: That one element is blocking an entire working page for no reason. Where oh where has web dev come to :'(
In 2013, I created a program to visualize what hosts a web site notifies when it is loaded http://daten.dieweltistgarnichtso.net/src/list-web-bugs.py – you can see the output for the article here: http://daten.dieweltistgarnichtso.net/pics/graphs/web-bugs/w...
Turning off the native component of anything always has consequences for those tinkering under the hood and the vast majority of those visiting that site don't tinker under the hood.
As the owner of a web dev company, I sometimes consider ignoring the "must work even without javascript" mantra. I haven't yet but there are times.
Fail gracefully was over the moment the "disable javascript" checkbox was removed from the options menu in every major browser.
There's a distinction to be made between content sites and application sites. It's really just too much work to try to make an application fall back to plain HTML, but for a content-centered site, like a blog, a news site, etc, it's not that hard to do things right and not require JS.
A browser which doesn't implement JavaScript is not crippled; it is 100% functional. A web page which requires JavaScript is crippled, because JavaScript is not required in order to display text and images.