-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor usability issue: block all scripts #3436
Comments
tomtom
changed the title
Usability issue: block all scripts
Minor usability issue: block all scripts
Jan 13, 2018
gorhill
added a commit
that referenced
this issue
Aug 31, 2018
<#3436>: a new per-site switch has been added, no-scripting, which purpose is to wholly disable/enable javascript for a given site. This new switch has precedence over all other ways javascript can be disabled, including precedence over dynamic filtering rules. The popup panel will report the number of script resources which have been seen by uBO for the current page. There is a minor inaccuracy to be fixed regarding the count, and which fix requires to extend request journaling. <#308>: the `noscript` tags will now be respected when the new no-scripting switch is in effect on a given site. A default setting has been added to the _Settings_ pane to disable/enable globally the new no-script switch, such that one can work in default-deny mode regarding javascript execution. <uBlockOrigin/uBlock-issues#155>: a new hidden setting, `requestJournalProcessPeriod`, has been added to allow controlling the delay before uBO internally process it's network request journal queue. Default to 1000 (milliseconds).
Will be great have also in Default behavior >Block popups for the users that want then allow per site. |
hawkeye116477
added a commit
to hawkeye116477/uBlock-for-firefox-legacy
that referenced
this issue
Oct 8, 2020
…es#155 <gorhill#95>: a new per-site switch has been added, no-scripting, which purpose is to wholly disable/enable javascript for a given site. This new switch has precedence over all other ways javascript can be disabled, including precedence over dynamic filtering rules. The popup panel will report the number of script resources which have been seen by uBO for the current page. There is a minor inaccuracy to be fixed regarding the count, and which fix requires to extend request journaling. <gorhill/uBlock#308>: the `noscript` tags will now be respected when the new no-scripting switch is in effect on a given site. A default setting has been added to the _Settings_ pane to disable/enable globally the new no-script switch, such that one can work in default-deny mode regarding javascript execution. <uBlockOrigin/uBlock-issues#155>: a new hidden setting, `requestJournalProcessPeriod`, has been added to allow controlling the delay before uBO internally process it's network request journal queue. Default to 1000 (milliseconds). Co-authored-by: gorhill <585534+gorhill@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
uBlock currently offers four general (medium mode) buttons to disable scripts: (1) inline scripts, (2) current page, (3) third party.
Let's assume some users usually want to disable scripts but want to whitelist some domains. They would have to gray out all three options. This is cumbersome.
IMHO it would be preferable if there were another option: (4) "all scripts" that comprises inline, current page & third-party scripts.
The text was updated successfully, but these errors were encountered: