Open GoogleCodeExporter opened 9 years ago
Scriptno also blocks Lastpass from functioning on untrusted sites - significant
collateral damage.
Scriptno's security model is preventing _users_ from running _user-side_ code,
with no way of creating exceptions AFAICT. If I want to use Lastpass to keep
my password & vimium to navigate, apparently I also have to allow that site to
run their own scripts on my machine, too.
Surely it would be desirable to distinguish between user-side & server-side.
Thanks, I want to use ScriptNo!
Original comment by ch...@singleys.com
on 4 Jun 2012 at 4:52
I'd also like to see this work with Vimium. I can't use this plugin if I can't
use Vimium too!
ch...@singleys.com has a good idea, distinguishing between server-side and user-side scripts.
Original comment by seso...@gmail.com
on 19 Jul 2012 at 7:09
See
http://code.google.com/p/scriptno/source/browse/wiki/FrequentlyAskedQuestions.wi
ki?r=44
Enabling "Respect Same-Domain" seems to allow Vimium to work on blocked domains.
Original comment by r...@rdodesigns.com
on 20 Sep 2012 at 12:59
Enabling "Respect Same-Domain" makes the extension about useless.
Original comment by daniele....@gmail.com
on 6 Nov 2012 at 2:56
You can fix them to work together by doing the following:
1. Go to the Extensions settings page
2. Enable developer mode
3. Copy the ID of the extension you want to run
4. Whitelist the ID as a domain name in ScriptNo's Options page
Original comment by lutos...@gmail.com
on 20 Jan 2013 at 10:25
Didn't work for me. Without Respect Same-Domain, extensions like vimium and
adblock don't work.
Anyone got it working?
Original comment by eduardo.eae@gmail.com
on 20 Jan 2013 at 11:19
#5 solution work for me (add extensions id to whitelist), thank.
my chromium(64bit) is: 27.0.1453.110 Debian jessie/sid (202711)
Original comment by johnw.m...@gmail.com
on 11 Jun 2013 at 2:34
testing more, #5 solution, sometime not work.
I agreed #4, Enabling "Respect Same-Domain" makes the extension about useless.
any better solution to solve this problem?
Original comment by johnw.m...@gmail.com
on 11 Jun 2013 at 3:06
I found the better solution, Add the id to whitelist, like #5,
and also add those extensions id to chromium/chrome built-in javascript
whitelist.
those extensions id added to two (javascript) whitelists,
now, all extensions work on all website for me.
thanks.
Original comment by johnw.m...@gmail.com
on 11 Jun 2013 at 3:44
Sorry, even add those id to two whitelists, on some website, some extensions
still not work.
Ammm :(
Original comment by johnw.m...@gmail.com
on 11 Jun 2013 at 3:48
Original issue reported on code.google.com by
mbsul...@gmail.com
on 16 Mar 2012 at 7:46