Blocking javascript per default enabled -> Exceptions are not saved

[boospy]

Hallo all,

I’m currently testing (I previously had noscript on Chrome) how “block scripts” behaves in Brave.

By default, I have JavaScript blocked. Now I open a website, e.g. https://steamcommunity.com/. I unblock some scripts (not all). The page reloads and everything works as it should.

But when I visit the site again later, ALL JavaScripts are blocked again. The scripts that I had previously enabled have to be re-enabled. The only option is to allow JavaScript for the whole website.

Is this normal behavior or am I making a mistake?

Thank you

[289wk]

@boospy

In your 2nd paragraph, “I unblock some scripts (not all)” ← exactly, how(?) do you do that, step by step ← please spell that all out (and in your detailed description, avoiding non-specific words such as “it”).

In your 3rd paragraph, “when I visit the site again later” ← exactly, what(?) did you do during the interim period. (Did you close the Brave Browser window? Did you close the Brave Browser tab? Did you quit Brave Browser? Did you restart the computer?)

Are there any extensions that you have added to Brave Browser? Are any of those extensions, for anti-virus, and/or ad-block purposes?

[boospy]

Thank for you reply. I’ve created some video (attached) what you can see how javascript is handelt with shield.

1. I’ve called this page, you see javascript is blocked
2. I authorize access to a few destinations via shield → the site works
3. Check again → yes, javascript is activated for some targets
4. Close the page and open it in a new tab.
5. The page no longer works, all scripts are blocked again → Control Shield

Are there any extensions that you have added to Brave Browser? Are any of those extensions, for anti-virus, and/or ad-block purposes?

A little of both. Besides, you can read things on many pages without ever getting the button to accept the mandatory cookies (or pay).

[289wk]

Thank you for the video - you did a VERY good job of moving the mouse arrow at a slow-enough pace that I could follow.

---

In a Brave Browser New Window, visit a website of interest. Let’s say, that is https://community.brave.com.

At the left end of the URL address field, to the left of the https, click on the “tune” icon; the result is a pop-down menu:

---

In that pop-down menu, ENABLE JavaScript:

and, reload the webpage.

---

In a Brave Browser New Window, go to: brave://settings/content

You should see under “Recent activity” the community.brave.com entry. Click on it:

The resulting page should be:

brave://settings/content/siteDetails?site=https%3A%2F%2Fcommunity.brave.com%2F

In the list of Permissions, scroll down to JavaScript

JavaScript ← ENABLE (Allow) that:

---

Close the brave://settings . . . window.

---

Reload the https://community.brave.com/ . . . window.

---

Click on the Site-Specific Brave Shields (the Lion) icon to the right, of the right end, of the URL address field.

In the resulting pop-down menu, you should see that the Site-Specific Brave Shields setting for JavaScript, is also ENABLED (Block scripts is DISABLED):

[boospy]

Thank you for the detailed answer, and yes, that would be an option. But it’s too complicated for my daily work. I will continue to use the workaround with “noscript”. It’s better suited to my way of working.

[Mattches]

I’ve opened the following issue for this, as I also believe that the allowed scripts settings should be retained when you revisit or reload the site:

Allowed scripts in Shields Panel should persist like other site-specific Shields settings

[289wk]

@Mattches

The issue that you opened above, might have some conflict with an issue that you opened a little while ago:

Custom filters permanently created when in private browsing

So the “bad” behavior here is that any information that occurs during Private browsing should not be saved or reflected anywhere else in the browser once Private browsing has ended. I’ll inform @fanboynz and some privacy folks about this.

Because, Brave is un-decided about what settings, and Shields settings, shall persist for:

• New Window
• New Private Window
• Private Browsing

There are Private JavaScript settings and Non-Private JavaScript settings.

Other than for testing (trying to help people, here at the Brave Community), I always use Private Windows, Private Browsing.

Regardless of my having a New Window open or a New Private Window open . . . or both . . . I need the JavaScript settings, the Brave Shields settings, the Site-Specific Brave Shields settings, to all persist.

I use the following type listings, because Brave Shields has inconsistencies, bugs, and failures to persist:

• [*.]cloudflare.com
• [*.]cloudflareinsights.com
• [*.]google.com
• [*.]googleapis.com
• [*.]gstatic.com

I expect those to work. And, by the way, sometimes they do solve problems for people who “cannot get YouTube to work properly.” Sometimes they do help people to “not get logged out.”

I need Custom Filters (my meager, but many, custom made AdBlock filters that I create to hide / block webpage elements) to persist.

Sincerely.

[Mattches]

I think that the first step to take here would be for this to work simply in standard browsing, which is what the issue is referring to. How those preferences are passed to private browsing sessions can be determined once the default behavior works as one would expect it to.