no-scripting: behind-the-scene false sticks even after restoring uBO from a config where it's not present #494
Comments
uBlock-user
changed the title
gorhill
added a commit
to gorhill/uBlock
that referenced
this issue
May 18, 2019
Related issue: - uBlockOrigin/uBlock-issues#214 Built-in whitelist directives are now rendered differently than user-defined whitelist directives. Also, removing a built-in whitelist directive will only cause that directive to be commented out, so that users do not have to remember built-in directives should they want to bring them back. Related issue: uBlockOrigin/uBlock-issues#494 The built-in per-site switch rule `no-scripting: behind-the-scene false` has been removed, it should not ever be needed since there will always be a valid root context for main- and sub-frames.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
no-scripting: behind-the-scene false appears in my rules when restoring uBO's configuration where it's not present.
Steps to Reproduce
Open My Rules and delete no-scripting: behind-the-scene false if present, now take a backup of uBO configuration or use mine--https://mega.nz/#!pNIVyaxS!lC0JN_sQewZI48wgyJuZH2c6iRo6jzDTJAjodBwYpAs
Restore uBO configuration from the backup you took or use mine from the aformentioned link
Open My Rules in dashboard and notice no-scripting: behind-the-scene false even though it's not present in the uBO config from which we restored the configuration.
Alternative STR by @gwarser -- https://github.com/orgs/uBlockOrigin/teams/ublock-issues-volunteers/discussions/85/comments/2
Expected behavior:
no-scripting: behind-the-scene false doesn't appear in My Rules when it was not present in the uBO config.
Actual behavior:
no-scripting: behind-the-scene false appears in My Rules even when it was not present in the uBO config.
Your environment
The text was updated successfully, but these errors were encountered: