Another red flag Doc doesn't mention here is the fact that Mozilla now requires extraordinary knowledge to disable JavaScript in Firefox.
There are broadly useful reasons to have this available as a toggle in the common UI (such as when you want to save an image from a site that uses JavaScript to prevent right clicks), yet it's hidden inside of the cryptic (to most users) about:config.
And why might this be? There could be several reasons all in play at once, including an attempt to protect users from themselves (think: The Nanny Browser), but I would just point out that the advertising infrastructure Mozilla increasingly relies on, with its cross-site user tracking, leans heavily on JavaScript.
It would appear that with that as a counter incentive, Mozilla has chosen to side with the ad networks, instead of with the users, in choosing which options to expose for easy control.
There are broadly useful reasons to have this available as a toggle in the common UI (such as when you want to save an image from a site that uses JavaScript to prevent right clicks), yet it's hidden inside of the cryptic (to most users) about:config.
And why might this be? There could be several reasons all in play at once, including an attempt to protect users from themselves (think: The Nanny Browser), but I would just point out that the advertising infrastructure Mozilla increasingly relies on, with its cross-site user tracking, leans heavily on JavaScript.
It would appear that with that as a counter incentive, Mozilla has chosen to side with the ad networks, instead of with the users, in choosing which options to expose for easy control.