"Disable JavaScript " Check Box Removed from Options/Preference from fx 23

Firefox has lost the setting to disable javascript with the upcoming version 23.
Reason given, there is a positive goal and it’s limiting the users ability to break their software.
Read: http://limi.net/checkboxes-that-kill/ link article author - Alex Limi.
The only extension that can block javascript to run now is NoScript.
Do you think the developers acted against the spirit of firefox with making disabling javascript only possible in the upcoming version via about:config
for developers, advanced users. What if there is no other way to close the browser window because of malcode?
No one thought of that example?
Chrome still has it in advanced settings…

What is the view of our users?
Is this browser now less of an “individual” browser, some may think that it is this development is “evil” or at least a bit “censorious”,

polonus

How much of an impact will this really have.I already run firefox with javascript enable and use NoScript. I have been doing this for a very long time and I have had no problems yet. If push come to shoves I can always get another browser.

Personally I think it will have little effect whatsoever, as most users would be none the wiser as they hadn’t sought to disable javascript.

Since javascript is pretty much a de-facto internet requirement as it is so widely used. For many they would never dream of disabling javascript and would be very likely to ruin their internet experience.

Whilst it can be used for malicious purposes as well as good, that is why we have security programs and add-ons like NoScript.

I think using firefox to disable all javascript is a poor choice, so I can understand why mozilla are thinking about removing the option to disable it.

I also wondered why FF would have so many setting that could broke your Internet connection or FF itself. I am relatively new to FF since I have always like my IE, but IE8 has have problems displaying some sites so switching to FF was the logical choice. However, if FF is choosing to eliminate some of the settings used for advance user, like polunus said, that can hinder its usability in some malcode cases, I do not see the improvement.

Firefox has always been my favorite browser and I will continue to use it. I’m not worried about disabling JavaScript.

Well I like the fact that firefox is so configurable - but general advice is to leave things on default settings for a while, certainly until you are familiar with it and always investigate what changes to the defaults may have on your browsing.

Like I said I am relatively new to FF and I like the about:config settings the most, but my experience at the beginning with my nephews was kind of trial an error. It seems that youngsters like a lot FF and like to click and flip anything to try and not remembered what they did afterward. So who do you think they call ? :wink: So the article got some truth to it, but on the other hand, for experts, its settings help a lot.

I like to point at situations like this:
“What to do When a Website Won’t let you Leave”
http://cyberarms.wordpress.com/2010/03/10/what-to-do-when-a-website-wont-let-you-leave/ (credits for example go to Helfdane)

What is the reason to take it out and reintroduce it with version 24 for web-developers,

polonus

A handy tip is to sort the about:config order by the Status column (just click the column header) and you/they can see all of the User Set entries easier.

As long as NS is supported, I’ve no problem with it.
Also, it will take my FF ESR a while to get there… :wink:

Yeap. I’ve done the Task Manager/End Task procedure with unwanted, unknown popups to avoid the “Not Now” or the “Red X”.

Thank you DavidR.