While disabling Javascript is something sure to break a lot of websites, it is something that I use regularly to test the websites that I am building so that I can confidently assert that disabling Javascript won't break MY website.
Same thing with disabling images. I have built web applications for the browser constrained (think remote science stations in Antarctica), and we often wish to test rendering without images (or with massively deferred image loading) or with only partial page renders to ensure that the first content loaded is the first content displayed for those situations where they are needed.
Sure, I'm a fringe case, but for some people, "breaking the internet" is a job requirement.
I'm not a UI guy, so my point wasn't whether or not the checkboxes should or shouldn't exist, but to clarify that all the use cases he asserted "broke the entire internet" had valid uses and represented the desired behavior.
That it happens to break a few popular websites doesn't mean that the entire internet is broken, or that that wasn't the desired effect.
While disabling Javascript is something sure to break a lot of websites, it is something that I use regularly to test the websites that I am building so that I can confidently assert that disabling Javascript won't break MY website.
Same thing with disabling images. I have built web applications for the browser constrained (think remote science stations in Antarctica), and we often wish to test rendering without images (or with massively deferred image loading) or with only partial page renders to ensure that the first content loaded is the first content displayed for those situations where they are needed.
Sure, I'm a fringe case, but for some people, "breaking the internet" is a job requirement.