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.
Feat.Req. Stop All Running Scripts Button.
Feat.Req. Stop All Running Scripts Button.
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0
Re: Feat.Req. Stop All Running Scripts Button.
+1, although this has the potential to be kind of a footgun...
*Always* check the changelogs BEFORE updating that important software!
-
-
- Posts: 5
- Joined: Tue May 12, 2015 6:01 am
Re: Feat.Req. Stop All Running Scripts Button.
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).
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).
Last edited by barbaz on Tue May 12, 2015 6:13 am, edited 1 time in total.
Reason: Fix link from risk of truncation
Reason: Fix link from risk of truncation
Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0
Re: Feat.Req. Stop All Running Scripts Button.
And that's why I said this feature request could be a footgun - "all running scripts" isn't limited to current tab.fluffypuff wrote:Bear in mind that this toggle affects all tabs (does not just suspend js processing in the currently active tab).
Do you know if that addon just toggle javascript.enabled or if it has its own logic to stop running scripts?
*Always* check the changelogs BEFORE updating that important software!
-
-
- Posts: 5
- Joined: Tue May 12, 2015 6:01 am
Re: Feat.Req. Stop All Running Scripts Button.
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
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).
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
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.great for freeing up resources, so that you are only using the scripts you really need at that time
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).
Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0
Re: Feat.Req. Stop All Running Scripts Button.
My apologies for using it thenfluffypuff wrote:Sigh. I really dislike the term "footgun".
Do you have an alternative that you would rather I use?
(linkification mine)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
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.
*Always* check the changelogs BEFORE updating that important software!
-
Re: Feat.Req. Stop All Running Scripts Button.
and +1 from Mc as well, who can't post here atm.
*Always* check the changelogs BEFORE updating that important software!
-