https://forum.palemoon.org/viewtopic.php?f=46&t=16504
on HN(2017): https://news.ycombinator.com/item?id=15112524
https://forum.palemoon.org/viewtopic.php?f=46&t=16504
on HN(2017): https://news.ycombinator.com/item?id=15112524
And I frankly don't see any problem with that.
The modern Web requires Javascript. Most major web sites will fail to work properly without it, often in confusing ways. (For example, Youtube will just display as a bunch of gray boxes.) Hiding a setting whose effect, for most users, is effectively to "break" the browser, is entirely appropriate.
I disagree.
There is nothing about the "modern" web which necessitates the use of JavaScript. I can understand the argument that, due to JavaScript's ubiquity, interfacing with some websites may prove impossible. But even then, that shortcoming isn't anything to do with the "modern" web; developers simply chose not to engineer a system capable of gracefully degrading.
The argument was not that the modern web requires devs to over-rely on JavaScript, forsaking all others and creating experiences which fail to function without it. The argument was that for the majority of users to interact with the majority of modern websites, JavaScript is required to be turned on. Which it is.
> ... for the majority of users to interact with the majority of modern websites, JavaScript is required to be turned on.
This is a self-inflicted wound.
You mean OCSP/CRL? Every browser does that.