ScriptSafe Extension Kills Vivaldi
-
I am running Vivaldi with the ScriptSafe extension on a Linux Mint 17.1 desktop system. I don't know whether the problem is Linux specific, so I am posting this question in the "All Platforms" section.
When I come to a web site I wish to allow, I tell ScriptSafe to allow it by clicking its "Allow" button. If I wish to allow the entire domain, I click the "Trust" button instead, as the instructions specify. However, as soon as I click the "Trust" button, Vivaldi closes. This happens every time I try the "Trust" button.
Has anyone else encountered this solution, on any platform? Has a solution been found?
-
Update: As an experiment, I launched the Chromium browser, installed ScriptSafe, and tried the Allow and Trust functions of ScriptSafe. In this case, both Allow and Trust worked just fine.
I then went back to Vivaldi and repeated the experiment. As before, Allow works OK, but Trust causes Vivaldi to shut down immediately.
I'm trying to think up more experiments to figure out this behavior. Any experience from other users of ScriptSafe would be helpful to hear.
-
After a lot more testing (including running it in Windows, running incognito vs normal mode, and other variants), I may have come upon the solution. It appears that, under certain circumstance, if you have already "Allowed" a certain page and then try to "Trust" the entire site, Vivaldi shuts down. You need to remove the page from your whitelist, then trust the whole site. This seems illogical to me. Trusting seems to be an augmentation of Allowing, rather than a conflict. However, ScriptSafe doesn't, for some reason.
I suppose I can chuck ScriptSafe altogether, and use the antiscripting feature in uBlock Origin. But the latter is not as comprehensive, as far as I can tell.
If I learn more, I'll check back in here, in case it might benefit someone else.
-
-