Ok, this just gets better and better, doesn't it.

I typed up a reasonable statement about this, that didn't make it with my post.

So now I look like captain obvious.

I really think it's time for me to move on to another browser.

hello, the option to toggle javascript is of course still there, but less obvious: enter about:config into the address bar and switch the preference called javascript.enabled or use an addon like https://addons.mozilla.org/firefox/addon/quickjava/ to do it conveniently.

Making all users pay the price for a tiny percentage of noobs who screw with their settings is the worst practice I can imagine.

You should have had a popup that would caution them that messing with javascript could make websites not function correctly. And that turning javascript back on, would solve the problem.

Instead, you guys chose to shoot a mouse with a bazooka.

And yes, i'm aware that it has been changed to about:config.

That's no comfort. It used to take me precisely 3 mouse clicks to accomplish this. And 3 clicks to turn it back on, since I always keep the option set to that tab.

Now I have to type in about:config in a blank web page, scroll down to one of more than a dozen javascript settings, of which I would have to google several times before I'll start remembering that setting, and then reverse all that when I go to a different website that I don't need javascript off.

Making that sound like it's no big deal, is intellectually dishonest. It's a very big deal to those of us who use that regularly.

And the idea of using an addon to acomplish this, is just absurd to me. Now I have to trust something that is so important that it's been hidden in the first place, to a third party application?

What "price" ? The browser is free! Add-ons are free, too.

What's absurd is assuming that the Firefox user support volunteers who answer questions here have anything to do with such UI modifications decisions.

With that extension only one click is needed vs 3 precise clicks as before. And it's not as if that extension is new, that extension has been around since 2005. Used it myself before NoScript came out, giving Firefox users domain by domain control of JavaScript.

It's an addon. And yes, I feel it is absurd to add more complexity of code to any software in order to accomplish the same thing. All this accomplished was to solve the problem of noobs screwing things up, when as I mentioned all it would have required is a nice popup window telling them that it is likely the setting would mess with web pages.

Also, I was not referring to a purchase price when I mentioned paying the price for noobs. It was a reference to the cost in time.

this is a community-run support forum, we are neither responsible for the changes mentioned nor can we do something about it - developers or UX designers won't read here, so your remarks are misplaced and will stay without any effect. please use https://input.mozilla.org/feedback to submit your feelings about the changes instead, which will be monitored by mozilla's staff...

Just to keep this discussion facts based, the tiny percentage of users is the ones who used disable javascript. Most users never do and alot of them accidentally switched it off for various reason (Didn't know what jS was, confusing it with java, etc.)

As mentioned by another user, the new mozilla policy is "we must protect users from themselves" and remove JS disable function.

This justification is not credible, there are other ways for newbie FF users to stuff things up.

What is the real reason for this clearly unpopular modification ?

Anything to do with the fact that disabling of JavaScript allows more anonymity online ?

Did a govt request FF do it ?

See this - http://limi.net/checkboxes-that-kill/

See this - https://bugzilla.mozilla.org/show_bug.cgi?id=873709

'The ability to disable JavaScript is now obfuscated, and users are deliberately discouraged against manipulating their JavaScript preferences. This is wrong, and inhibits a users understanding of what happens when they load a web page.

The following is not an acceptable work around: about:config > javascript.enabled'

Hello MKULTRA, see :

• http://limi.net/checkboxes-that-kill/

• Bug 851698 - (checkboxes-that-kill) Get rid of options that kill our product

thank you

It is an acceptable workaround, as are the multitude of add-ons you can install to replicate this behavior. This is turning away from a support thread and into a rant, again. Rants don't belong here.

See also:

• YesScript: https://addons.mozilla.org/firefox/addon/yesscript/
• QuickJava: https://addons.mozilla.org/firefox/addon/quickjava/

here is a question why are we relying so heavily on java script ? the problem here is not the options but the website it self.

if you have an issue with a website take it up with them not the browser unless it is a genuine bug so why is Firefox catering for the Incompetent webdevs who don't know what compatibility is

Alex Limi sounds like a "looks good on paper" guy if you look hard enough everything has bugs

as for add-ons why disable something that you have to re-enable with a work-a-round sounds dumb

if it aint broke don't fix it