4 ms·
So what about "Disable Javascript" option to be removed in Firefox 23? Was it? That is a dealbreaker for me.
by CapitalistCartr 13y ago
So what about "Disable Javascript" option to be removed in Firefox 23? Was it? That is a dealbreaker for me.
- cyphax 13y agoThey removed the checkbox from the options but if you look in about:config you can disable Javascript. So that's a yes and a no? :P
- ender7 13y agoIt was, but there are many addons that will turn it off for you.
- babuskov 13y agoI'm using web developer extension anyway. Disabling/enabling JS is a matter of 2 clicks in its menu.
- _greim_ 13y agoAlso a dealbreaker, no "disable HTML" option. It's critical to my daily workflow to be able to turn off all content and browse the web in peace and silence.
- nsmartt 13y agoThe idea is that non-technical users shouldn't have options in preferences that will break the web for them, and that technical users will use about:config or an add-on (e.g. NoScript). I find it difficult to argue with that. edit: clarity. total rewrite.
- Gormo 13y ago"Non-technical users" is a contradiction in terms. If you're using technology, you're a "technical user". If you don't know how certain options work, you should leave them alone; but if you don't leave them alone and something breaks, it takes only common sense and not specialized knowledge to suspect that the thing you changed has some relationship to the thing that broke. De-featuring software for the presumptive convenience of a presumptive lowest-common-denominator user is not a good practice.
- smackfu 13y agoYour vision of users is so adorable. Real people just don't act that way.
- Gormo 13y agoSo the people who do act that way are fake people? I've worked a helpdesk, and I know where the stereotypes are coming from. I also know that selection bias is selection bias, and that there's never an excuse to remove functionality from software.
- bashinator 13y agoGood thing no functionality has been removed, then.
- Gormo 13y agoThe release notes did say "removed"; apparently, this is inaccurate.
- nsmartt 13y agoIt's true that users should not break things without some mind as to how to fix them, but it's also irrelevant. If a user breaks your product, it makes no difference to him or her who broke it. It's still broken. Users will have a bad experience. This doesn't mean advanced options shouldn't exist, but it does mean that they should be out of the way for non-advanced users. In this case, the setting is moved to about:config or to add-ons, so I don't see how we've lost anything. Are you opining that some users may not be able to find the setting in about:config? Would they not just enter "How to disable JavaScript in new Firefox" into a search engine? >"Non-technical users" is a contradiction in terms. If you're using technology, you're a "technical user". This is a debate about semantics. "Non-technical" is a colloquialism. I see no benefit to this train of thought.
- Gormo 13y ago
- millerm 13y agoWell, for savvy users: In the location bar type about:config Search for javascript.enabled You can turn it off there by simply double-clicking the entry.
- stephen_g 13y agoThey should have just renamed it "Break almost every web site" instead.
- oneeyedpigeon 13y agoCitation required for the claim that "almost every" web site is so badly put together that it breaks if you show up without JS.
- hrjet 13y agoI am disappointed too. Although it's not a deal breaker for me (I am savvy enough to use about:config, NoScript, etc), I think this is bad for users in general. Many of them are not tech-savvy enough to dig into hidden configuration options. Though they certainly deserve better security when they browse the web.