Scriptsafe breaks vivaldi
-
Hi, i just installed scriptsafe. It worked well. But when you close vivaldi and reopen vivaldi it does not start anymore. Is this a bug of vivaldi ore is it scriptsafe?
-
Hi Gwen
I had to deinstall vivaldi completely…
Only deinstall vivaldi was not enough to get it working again.But i was lucky it was only on my win10 gaming partition. My mint is not affected puh ^^ (Note to me: I really need a Bookmark backup).
So just for testing i installed beta 3 instead of latest snapshot there scriptsafe is working well.
Greetings
-
I'm having the same issues with Vivaldi (32bit) on Win 10 and ScriptSafe
I was so glad to hear that I could use Vivaldi with my well known extensions from Chrome but without a good script blocker I'm not going anywhere in the internet ^^Does anyone know a similar extensions that is currently working?
I may try the combination on my Ubuntu soon.
-
Same issue. Once scriptsafe is installed and vivaldi is closed it won't start up anymore. Hoping to have a fix sometime soon because otherwise I love this browser.
-
Anyone know if this has been fixed yet?
-
There's been no mention of a fix.
Keep in mind the Vivaldi UI is mostly javascript. Hence, script blockers block it. Trying to get script blockers to work while not interfering with the UI is going to be a bit of a tightrope act, I fear.
-
A key ingredient of the Vivaldi interface is javascript. That might be a place to start.
-
@Aerya:
Trying to get script blockers to work while not interfering with the UI is going to be a bit of a tightrope act, I fear.
Hi,
That sounds like a prob if "you" (or "we", users) want to make Vivaldi a safe browser. I'm testing ScriptSafe since on yesterday to understand what's breaking V, already reinstalled it about 20 times… Hopefully its ok with uMatrix but that's not really the same goal.
Any idea on which parameter could be breaking V or to bypass this maybe with a rule?
Thank you,EDIT: BTW I'm using ArchLinux but posted here after searching for "scriptsafe".
Many websites use JavaScript all the time in their site code. Vivaldi's user interface is coded mostly in JavaScript. One ought to be kept separate from the other with regards to a script-blocking extension's own execution, but that doesn't always work out in practice as it might in theory. If the script-blocking extension interferes with the browser's own JavaScript execution, problems will occur; likewise, if the browser's JavaScript somehow co-mingles itself with the website's scripting during some phase of browser operation, that too can make for a browser-induced issue and cause problems. Frankly, while I'm a JavaScript-blocking advocate by nature, it's probably 'early days' to expect that sort of thing to work flawlessly (if at all) in Vivaldi at this point.
-
Seems to be working quite well for me now. Only thing is that pages won't reload when scriptsafe allows or blocks something.
-