Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

add noScriptInfo checkboxes to allow scripts by origin #7272

Merged
merged 1 commit into from
Feb 22, 2017
Merged

Conversation

diracdeltas
Copy link
Member

@diracdeltas diracdeltas commented Feb 16, 2017

test plan:

  1. disable scripts globally in about:preferences
  2. go to vox.com. images should not appear.
  3. click on the noscript icon
  4. unselect everything except vox.com and vox-cdn.com and click one of the 'allow' buttons
  5. images should appear
  6. click on the noscript icon. you should see a bunch of origins but not vox.com and vox-cdn.com

fix #6431. adjusts the noScriptInfo dialog so that it can be used to allow scripts by origin, instead of all scripts on the page, when NoScript is globally enabled. removes the option to allow scripts persistently (since this can be done via the Bravery panel anyway)

auditors: @bbondy

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Ran git rebase -i to squash commits (if needed).

screen shot 2017-02-15 at 10 45 06 pm

@diracdeltas diracdeltas added this to the 0.13.6 milestone Feb 16, 2017
@diracdeltas diracdeltas modified the milestones: 0.13.5, 0.13.6 Feb 16, 2017
@@ -660,6 +660,18 @@ Dispatches a message when a tab is being cloned



### setNoScriptExceptions(hostPattern, origins)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we're trying to avoid set* names for actions, and name them after an event instead. Could you rename this to noScriptExceptionAdded or something similar?

*/
setNoScriptExceptions: function (hostPattern, origins) {
AppDispatcher.dispatch({
actionType: appConstants.APP_SET_NOSCRIPT_EXCEPTIONS,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto this constant


.truncate {
margin-bottom: 5px;
}
.noScriptCheckbox {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're using aphrodite for new UI but since this isn't new UI and just an extension of an existing one this is cool. Feel free to update at the same time to aphrodite if you want to.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sgtm!

@bbondy
Copy link
Member

bbondy commented Feb 21, 2017

ack sorry I had review comments pending and didn't notice.

fix #6431. adjusts the noScriptInfo dialog so that it can be used to allow scripts by origin, instead of all scripts on the page, when NoScript is globally enabled. removes the option to allow scripts persistently (since this can be done via the Bravery panel anyway)

auditors: @bbondy
@diracdeltas
Copy link
Member Author

@bbondy addressed review comments

@bbondy
Copy link
Member

bbondy commented Feb 22, 2017

++

@k-ninja
Copy link

k-ninja commented Aug 3, 2017

Why is there no option to permanently whitelist domains for script execution? It's not a great user experience to have to re-enable scripts for my internet banking every time I restart my browser.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature to allow scripts by origin
5 participants