notscripts prevents the use of bookmarklets unless "Allow all" is active about notscripts

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Clicking on the bookmarklet sometimes triggers the appearance of the site 
hosting the script, in the NotScripts menu.

Original comment by sebism on 1 Nov 2010 at 12:16

[GoogleCodeExporter]

I just wanted to mention that I may stop using NotScripts because of this bug.  
I just started using it, and I'm finding it pretty great other than this 
problem.  I haven't been using it for long enough to decide how much of a 
problem this will be, but I suspect that it will drive me away from NotScripts, 
at least until this issue is resolved.

It's also noteworkthy that even a really simple bookmarklet will cause 
problems.  For example, using the bookmarklet `javascript:alert('hello')` will 
cause the page to turn blank.

Original comment by [email protected] on 25 Dec 2010 at 8:48

[GoogleCodeExporter]

Definitely a problem.

Original comment by [email protected] on 13 Apr 2012 at 3:59

[GoogleCodeExporter]

I have this problem as well.  I use a bookmarklet to remove "styles" from pages 
I find obnoxious to read (e.g. pages that have white text on a black 
background).  The bookmarklet I use is:

javascript:(function(){var%20newSS,%20styles='*%20%20%20{%20background:%20#fff%2
0!%20important;%20color:%20#000%20!important%20;%20font-family:%20verdana,%20san
s-serif%20!important%20;%20font-weight:%20normal%20!important%20;%20%20}%20:link
,%20:link%20*%20%20%20{%20color:%20#00f%20!important%20%20%20}%20:visited,%20:vi
sited%20*%20%20%20{%20color:%20#60c%20!important%20%20%20}';%20if(document.creat
eStyleSheet)%20%20%20{%20document.createStyleSheet("javascript:'"+styles+"'");%2
0%20%20}%20else%20%20%20{%20newSS=document.createElement('link');%20newSS.rel='s
tylesheet';%20newSS.href='data:text/css,'+escape(styles);%20document.getElements
ByTagName("head")[0].appendChild(newSS);%20%20%20}%20})();

Please include a way to whitelist bookmarklets from our bookmarks.  I'm 
surprised to see this bug goes back over 2 years, with no owner, and no sign 
that anyone is working on it.

Original comment by [email protected] on 4 Feb 2013 at 6:39