InformAction Forums

Feature request.

a "Stop All Running Scripts Button".

maybe just as a menu option, but i think in those instances where scripts are chewing up resources, an upfront button (or keybind?) would be better to restore useability when the system is choked out by scripts.

the "revoke temporary permissions" is nice, but there are times when one needs to stop all scripts.

great for freeing up resources, so that you are only using the scripts you really need at that time, killing off all the superfluous scripts with one click.

+1, although this has the potential to be kind of a footgun...

Digit, in the meantime while waiting/hoping the feature will be added
This ff extension provides a toolbar button to achieve on-the-fly javascript enabled/disabled toggle:
https://addons.mozilla.org/en-US/firefo ... cktoggles/
Bear in mind that this toggle affects all tabs (does not just suspend js processing in the currently active tab).

fluffypuff wrote:Bear in mind that this toggle affects all tabs (does not just suspend js processing in the currently active tab).

And that's why I said this feature request could be a footgun - "all running scripts" isn't limited to current tab.

Do you know if that addon just toggle javascript.enabled or if it has its own logic to stop running scripts?

Sigh. I really dislike the term "footgun".

The QuickToggles extension simply uses prefService to toggle the value.
However, sometimes the result amounts to "pausing" rather than outright stopping/aborting certain scripts.
From experimenting with its effect on various script demo pages at the www.jsdo.it site, seems like code within setTimeout() wrappers is often pause-able/recoverable.

Here's an older extension which targets docShell properties of individual gBrowser tabs, providing control on a per-tab basis:
https:// addons.mozilla.org/en-US/firefox/addon/tab-permissions
Interestingly (to me), this extension is able to enforce "inheritance" permissions ~~ docShell of tabs opened by links clicked in a restricted tab will 'inherit' the restriction.
Another extension that enforces inheritance: "Disallow Scripts Button" https:// addons.mozilla.org/en-US/firefox/addon/disallow-script-button

great for freeing up resources, so that you are only using the scripts you really need at that time

Ah, I'm only considering freeing CPU resources. Other extensions exist to suspend/unload background tabs, but that really seems beyond the scope of a noScript feature request.

The extensions I mentioned above, and the prospect of noScript providing a (contextMenu? toobar?) toggle control
represent achieving a night-and-day difference, in terms of multi-tab usability, on an older/underpowered CPU.
Also -- and, actually, the reason I went searching for a "toggle" -- ability to suppress incessant ajax callouts (and/or disk churning, due to the requests being logged).

fluffypuff wrote:Sigh. I really dislike the term "footgun".

My apologies for using it then
Do you have an alternative that you would rather I use?

fluffypuff wrote:The QuickToggles extension simply uses prefService to toggle the value.
However, sometimes the result amounts to "pausing" rather than outright stopping/aborting certain scripts.
From experimenting with its effect on various script demo pages at the www.jsdo.it site, seems like code within setTimeout() wrappers is often pause-able/recoverable.

Here's an older extension which targets docShell properties of individual gBrowser tabs, providing control on a per-tab basis:
https://addons.mozilla.org/en-US/firefo ... ermissions
Interestingly (to me), this extension is able to enforce "inheritance" permissions ~~ docShell of tabs opened by links clicked in a restricted tab will 'inherit' the restriction.
Another extension that enforces inheritance: "Disallow Scripts Button" https://addons.mozilla.org/en-US/firefo ... ipt-button

(linkification mine)
Thank you for the details.

Come to think of it, NoScript may already have some of the machinery needed: https://noscript.net/changelog#2.6.8.20rc2
I'd have to look at that diff and the other addons' code to see what approach is the "nicest" and most effective for this.

and +1 from Mc as well, who can't post here atm.