> if the scripting media query was ubiquitous I would never go back to toggling classes via JS
I am asserting that in the majority of cases where a person's browser is not running a page's JavaScript, it is because of a network failure or intentional blocking, neither of which can be detected by the media query.
Therefore, three years from now when the media query will be ubiquitous, it won't prevent your styles that are meant to be used only with your JavaScript from being used most of the time.
The `@media (scripting: none)` query absolutely can detect if a user has disabled JS on the page via their browser's settings (e.g. via chrome://settings/content/javascript). If you mean to say that it can't detect when a third party extension has disabled scripts, well then I would say that's personally out of scope for me. Extensions can do all sorts of nefarious things, the least of which is disable JS. As far as network reliability is concerned, if the user can't download fonts, media files, stylesheets, scripts, and linked pages, then toggling classes is probably the least of my concerns.
I am asserting that in the majority of cases where a person's browser is not running a page's JavaScript, it is because of a network failure or intentional blocking, neither of which can be detected by the media query.
Therefore, three years from now when the media query will be ubiquitous, it won't prevent your styles that are meant to be used only with your JavaScript from being used most of the time.