Chrome 34 and Scriptsafe
GoogleCodeExporter opened this issue · comments
It seems to me that ScriptSafe has some issue when running on Chrome 34. After
updating Chrome to this version, ScriptSafe begun to suddenly crash. With
"crash" I mean that the button just is red for all pages (also already trusted
sites) and that ScriptSafe seems not to work (block) at all.
I attached a screenshot of the ScriptSafe menu when it crashed...
What version of the product are you using? On what operating system?
1.0.6.16 on Chrome 34.0.1847.116 m Windows 7
Original issue reported on code.google.com by matthias...@gmail.com on 16 Apr 2014 at 10:32
Attachments:
I have the same issue. Not blocking anything
Uninstalled scriptsafe and re-installed, restarted Chrome and it worked until a
reboot.
ScriptSafe v1.0.6.16 Chrome Version 34.0.1847.116 m Windows 7 64
Original comment by alad...@gmail.com on 17 Apr 2014 at 12:52
- Added labels: ****
- Removed labels: ****
[deleted comment]
Same issue here. ScriptSafe v1.0.6.16, Chrome Version 34.0.1847.116 m, Windows
7 Home Premium SP1 with all available updates.
ETA: I went to a site I know I hadn't gone to before but knew would probably be
trustworthy: yankeecandle.com. Checking the DevTools Elements, the only js
blocked were done by AdBlockPlus, so I think ScriptNo is effectively disabled
at the moment. Not sure if it's throwing an error that make Chrome stop it or
what.
Also, on the ScriptNo options page, the whitelist and blacklist are both blank
(see image). I don't know where those settings are saved, so I can't check if
the lists are actually gone.
Original comment by mandy...@gmail.com on 20 Apr 2014 at 3:38
- Added labels: ****
- Removed labels: ****
Attachments:
I actually got mine working again! And my whitelist is intact. I think all I
did was uninstall ScriptSafe, close chrome, open, reinstall it, then click
"sync FROM Google" button, which I was glad actually worked after accidentally
clicking "sync TO" while the problem was happening... I did have a feeling that
all the script event triggers on the options page weren't firing anyway.
Original comment by nj.clare...@gmail.com on 22 Apr 2014 at 2:56
- Added labels: ****
- Removed labels: ****
actually... maybe not. i got the primary domain showing green/red, but no other
domains' scripts are showing. not sure if it's actually blocking anything...
Original comment by nj.clare...@gmail.com on 22 Apr 2014 at 4:05
- Added labels: ****
- Removed labels: ****
At the moment the issue seems to be solved for me too... I did nothing
special... I also removed scriptsafe from Chrome and re-installed it. But i'm
not sure if this solved the problem...
Original comment by matthias...@gmail.com on 23 Apr 2014 at 6:43
- Added labels: ****
- Removed labels: ****
Sorry, I should not have said that it's working again. I wrote this comment and
went back to another tab and there it was again... same issue as before...
Original comment by matthias...@gmail.com on 23 Apr 2014 at 6:51
- Added labels: ****
- Removed labels: ****
There was a Chrome update that I "forced" today by visiting about:help. That
seemed to fix it. I had many browser restarts and troubleshooting attempts over
the past week or more, but obviously they reverted whatever change that broke
us. I'm not a programmer, but I didn't see anything in the changelog that stood
out to me.
Original comment by nj.clare...@gmail.com on 26 Apr 2014 at 11:13
- Added labels: ****
- Removed labels: ****
I tried nj.clare's solution and have been browsing around a bit without
scriptno dying. The update to 34.0.1847.131 m seems to be a good solution.
Thanks for the info, nj.clare.
Original comment by mandy...@gmail.com on 26 Apr 2014 at 12:32
- Added labels: ****
- Removed labels: ****
The only thing that works for me is a temporary solution. When I start up
chrome for the first time each day, I disable ScriptSafe then re-enable it.
From that point everything works normally. Only tabs you open after you have
done this work normally. If you completely exit chrome (not running in
background), you'll have to do this again.
Original comment by pthubb...@gmail.com on 1 May 2014 at 9:35
- Added labels: ****
- Removed labels: ****