I can't even reproduce this in Chrome (disabling JS via the dev tools).
We have implemented the standard method (JsOnly). If JS gets disabled and <noscript> is handled badly (and I have seen this before when forcing JS off via an extension), there's not much we can do.