I was able to do this with v1 of Shields but no longer. I just want to allow javascript for the main page for the games I play and not all the other scripts. No idea what I am looking at on the FilterLists page. There is no need to make a filter list by yourself word by word. we can help you with the syntax for that if you want to go this route, but umatrix/noscript are much more usable for most people If you don’t feel like installing an extension and know what scripts you want to disable or selectively enable, you can write a custom adblock filter in brave://settings/shields/filters. Umatrix and noscript are reasonable alternatives However, that being said, we will revisit the feature if we can find an easier way to re-implement given Chromium internals, or if we believe a significant portion of Brave users would use the feature if made available again
Thats not to say that per-script controls aren’t still useful, just that they’re useful in less cases than they were previously. For example, Brave ships ephemeral, partitioned storage and randomized fingerprint protections by default (among many other features) dramatically reducing how much privacy harm most scripts can cause. Brave shipped a number of other on-by-default privacy features that reduced the privacy-benefit of the per-script-controls.For example, Brave ships ephemeral, partitioned storage and randomized fingerprint protections by default (among many other features) dramatically reducing how…
#UNGOOGLED CHROMIUM LINUX MINT UPDATE#
Related post from Brave staff with background information:īrave Shields panel individual javascript source selection - Allow function - lost with Browser v1.38.109 update - #16 by pesįeature to allow individual scripts is gone in Brave Shield v2 #22601īring back one time script blocking New Feature FeedbackĪlso, just to give some context to why the per-script controls were removed from Brave in the first place, we decided to remove the feature for three reasons:īrave shipped a number of other on-by-default privacy features that reduced the privacy-benefit of the per-script-controls.
The feature and workaround as provided in previous versions has been removed. ISSUE: Shields Blocked Scripts “Allow Specific Scripts” Option Selected Topics: Brave GitHub → In the Works: Selected GitHub Issues/Projects → ANNOYANCE ISSUES: Source: User Solutions: Brave Release 1.42.x Why would I want to have all those other scripts with potential privacy issues enabled? I do not have any desire to save or track Wordle results or settings. Take Wordle for example, you could play with just enabling javascript and not the umpteen other scripts enabled when you disable block scripts.
0 kommentar(er)
