as you've obviously got an axe to grind
My only axe to grind is with someone who treats me like an idiot because I don't think I should have to write an add-on to do something that used to be a simple checkbox menu item. Someone who thinks THEIR solution to a problem they've never come across is so much better.
The JS toggle in settings is global. If you have multiple tabs open, it gets turned off for ALL tabs, not just the malicious page.
Do'h. I know that. So what? Once you get rid of the malicious page that you can't get away from while js is active, TURN JAVASCRIPT BACK ON. It really is that simple. Three simple steps: 1. Turn js off. 2. Escape the malicious page. 3. Turn js on.
If some other webpage cannot survive with javascript off for ten seconds and you may lose so much precious data because of it, just imagine how much precious data you'll lose when you have to kill the browser and reload the page from scratch.
But then on the other side, loading a banking page in the same browser as a potentially untrusted page at the same time isn't really a good idea in the first place.
You make it sound like I'm saying I go visit my bank and then decide to go look at malicious websites just for fun. That demonstrates a complete lack of comprehension of the problem and is patently insulting to boot.
You're the one who brought up loading banking pages after a malicious web page gets control. I told you how you solve the incredibly difficult problem of having a banking page that needs js -- by simply not disabling js when you go there.
This global toggle wasn't an issue back when it existed, as web pages would load their JS on load, and that would be that -- so you'd just turn JS off, reload the malicious page,
Now I know you're trolling. Why the fuck would I reload a malicious page once I've managed to get away from it? The goal is NOT to be there at all, not to see what it looks like without javascript enabled. But then, you've said you've never been on one, so you don't know.
And my copy of firefox takes as long to close and re-open like this as navigating to the Prefs/Options and toggling JS would take.
I understand. You got yours. A feature THAT YOU WOULDN'T USE ANYWAY cannot be tolerated because ... I don't know, because you might lose control of your own mouse and wind up using it and not know why all your favorite websites no longer work like you want them to? You think that it should be impossible to have a simple option to do something simple and you want to force others to create an add-on. Your machine and network connection is fast enough to reload twenty or thirty tabs so killing the browser and hoping you uncheck the right miscreant if/when you get offered the chance is the only option anyone needs.
And I get that you think other people are too stupid to be able to manage a simple checkbox to turn javascript off. You make that clear when you talk about deliberately going to malicious websites while I'm doing my banking ("But then on the other side, loading a banking page in the same browser as a potentially untrusted page at the same time isn't really a good idea in the first place.") or how I want to reload the malicious web page I've just managed to get away from. Stop treating other people like idiots because they want an option PUT BACK (not created, just put back) that you don't intend on using.
Every reason you have for not allowing a simple option to disable javascript boils down to two: it might break some web page if javascript isn't on, and nobody could be smart enough to turn javascript back on when going to such a page. To the first, boo friken hoo, and to the second, <expletive deleted>.