search

thoroc / scriptno

Automatically exported from code.google.com/p/scriptno
1 stars 0 forks source link

1.0.6.9 resources still broken in Chromium #155

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Click on resources.
2. Resources are empty.
3. Running version 1.0.6.9 on Version 20.0.1132.47 Built on Ubuntu 12.04, 
running on LinuxMint 13 (144678)

What is the expected output? What do you see instead?
I expect to see resources.

Seeing Instead:
Resources (hover each to see paths) 
Andrew Y. | Quick Start | Overview | Project | FAQsOptions | ScriptSafe 
v1.0.6.9 | 

What version of the product are you using? On what operating system?
See above.

Please provide any additional information below.
Tried disabling/enabling extension, and stopping/starting ScriptSafe.

Original issue reported on code.google.com by whin...@gmail.com on 30 Dec 2012 at 1:30

GoogleCodeExporter commented 9 years ago 
I had the same Issue on OS X and Linux (LMDE). 

On OSX I could fix the problem with enabling/disabling the extention *and* 
reloading the tabs.

On LMDE I had to remove and to reinstall the extention *and* after 
reinstallation I had to reload the tabs.

ScriptSafe is momentary in sad, problematic and potential dangerous state! :-O

Original comment by thosch.gmx.de on 30 Dec 2012 at 12:14

GoogleCodeExporter commented 9 years ago 
Same problems here. Additionally, it seems impossible to change any options. 
The "Save" and "Close" buttons just don't do anything. Mac OS X 10.6.8, Chrome 
24.0.1312.45 beta, ScriptSafe 1.0.6.9. I'm willing to help with beta testing.

Original comment by wil...@gmail.com on 30 Dec 2012 at 1:08

GoogleCodeExporter commented 9 years ago 
@ wil...@gmail.com

Did you remove and reinstall ScriptSafe. This fixed the problem for me on 
Linux. Should also work on OS X.

Original comment by thosch.gmx.de on 30 Dec 2012 at 1:23

GoogleCodeExporter commented 9 years ago 
Removing / reinstalling the ScriptSafe extension did the trick, but only after 
another Chromium restart. Thanks!

Original comment by whin...@gmail.com on 30 Dec 2012 at 1:32