Interesting selective response.
I responded to what I found relevant.
I proposed a complicated by-page or by-site manager as something that won't break other open tabs. Feel free to propose something better, like NoScript.
I responded to your complicated system by pointing out how overly complicated it was. I proposed something better.
The global toggle breaks things.
Yes, I know. If you disable jt, it breaks every webpage that relies on javascript to do anything useful. It also breaks every website that relies on js to do malicious things. That's good.
The fact that it DID work for you in a specific use case back when it existed doesn't say anything about today.
Since it still works today, yes, today's use case is adequately covered. I still have systems with that version and they run just fine. Nothing is broken. Having the option to turn off js didn't break any pages. Why would it? They don't know you have the option unless you use it to stop them from doing something malicious. If that's the case, then boo frigging hoo the page is broken by turning off js.
I challenge you to make an add-on that does only one thing: toggles Javascript.
I shouldn't have to learn how to write a full add-on to do something that WAS THERE AND WAS REMOVED, just to TURN OFF something. That's ridiculous. And the problem is that if the malicious website is preventing you from getting to any other pages you are probably going to have trouble getting to the add-on.
-- breaking banking pages, search pages, webmail pages, etc. is not so good.
Here's an idea. What about DON'T TURN OFF JAVASCRIPT ON PAGES THAT AREN'T MALICIOUSLY TRYING TO HIJACK YOUR "WEB EXPERIENCE"? It's that simple. Really. There's no reason to turn it off for banking, search, etc unless they are doing something bad.
I run into problems even when using NoScript, which has more advanced features to mitigate the issues resulting from Javascript vanishing unexpectedly on loaded pages.
You run into problems because you have a add-on that's playing games with what sites can and can't use what code. It's much simple to say "no javascript". You know how many times I've run into problems with javascript "vanishing" on loaded pages? ZERO. At WORST the page complains about not having javascript and I just go turn it back on. A couple clicks of the mouse and solution achieved.
You know what my replacement for the JS toggle was?
If a page starts messing with me, I close my browser down completely.
And when you start back up it reloads all the pages, including the one that you wanted to get away from. And it takes the time to reload all the other pages. Yes, I've sometimes seen the "Oops" page that first asks which pages to reload, but more often than not it just reloads everything. And if the js is messing with other pages, you get the messed result right back.
It is just more convenient and less time consuming to turn off js when necessary than to kill a browser session and wind up back where you were.
I then add said page to AdBlock.
What does this have to do with blocking ads? Where did you get the idea that ads are the only malicious web pages our there?