Absolutely correct that just about any website on the net will need a good portion of adjustments made using various script blockers just to get the site to even work at all.
A good example involves just the simple website “mapquest” which if using “Umatrix” will need 9 scripts enabled just so the website works that are blocked by default using “Umatrix” and of course unless you want to always have to enable these 9 scripts every time you use “mapquest” when you find it’s not working at all you’ll want to “lock” this “temporary” setting in for that site (scope) so next time the site works up front. Obviously it can be very time consuming surfing the web just to try and be safe and to be honest far to daunting for the “casual” user, but that’s the way of it unfortunately. There is frankly a lot of trial and error just to find out what needs to be enabled and what doesn’t need to be enabled as far as all the blocked items.
After awhile you get to the point you want to just enable them all for the time being to just get done what you want done at the time. This is to some degree the advantage using the FF “NoScript” which allows the user to either “temporarily” enable specific items but more importantly as risky as it might be when sites have literally dozens upon dozens of blocked sites the user can “temporarily” enable “all this page” with just one click which of course is not necessarily very SAFE and as such probably not advisable but at times I find myself doing this now and then just to accomplish something I need quickly in the knowledge that the setting is just “temporary” and will revert back later. Of course on can enable all the sites in “Umatrix” but it’s more time consuming because each needs to be enable individually in groups, which in some ways maybe arguably better because it conceivably forces the user to be more safe with less global automation at their fingertips. The Chrome “Umatrix” does have a nice feel about it as well however. I also find that “Umatrix” will default a lot as enabled so in some cases websites will be more functional than other script blockers that block everything from the start by default, but then safety is the trade off I suppose. All this security frankly takes a lot of fun out of surfing the web for the “casual” user which clearly makes these script blockers seem annoying to these these type of users not to mention totally confusing in many respects as well.
I would add one last thing that’s nice about the FF “NoScript” and that is the user can “middle click” any blocked site and get 6 different security reports on that site which can then be “enabled” or not on that page which is a helpful feature provided by the FF “NoScript”. Also even if you want to Allow “all scripts globally” (not at all advised), or your just Allowing “all this page” for the time being “NoScript” still retains several areas of security anyway like in the case of Anti-XSS protection, HTTPS enforcement, Clickjacking protection and ABE which are all still in effect regardless which is another helpful feature of the FF “NoScript”.
