search

TetragrammatonHermit / scriptno

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

No allowed or blocked resources listed? #255

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Going to any site and clicking on the Scriptno button.

What is the expected output? What do you see instead?

I was hoping to see a list of all the sites that were blocked and allowed, and 
what exactly was being blocked or allowed so that I could manage my white- and 
blacklists. When I go to a site, however, such as this one (code.google.com), I 
am informed that no external resources were loaded (which isn't true; see 
below), so I really don't get nearly the information from Scriptno that I was 
expecting to.

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

ScriptSafe v1.0.6.16, under Chrome 34.0.1847.116, under Mac OS X 10.9.2.

Please provide any additional information below.

AdBlock shows the following resources:

    https://ssl.google-analytics.com/ga.js [script; blocked by AdBlock]
    https://code.google.com/apis/ajax/playground/get_projects [xmlhttprequest   ]
    https://code.google.com/hosting/multilogin [xmlhttprequest]
    https://code.google.com/hosting/projects [xmlhttprequest]
    https://d3ijcis4e2ziok.cloudfront.net/tpc-check.html [frame]
    https://ssl.gstatic.com/codesite/ph/images/star_on.gif [image]

So clearly, google-analytics.com, cloudfront.net and gstatic.com are external 
resources; only google-analytics.com has been blocked by AdBlock. I'm not using 
any other installed blocking mechanisms that I am aware of.

Original issue reported on code.google.com by ken.mcgl...@gmail.com on 25 Apr 2014 at 9:54

Attachments:

GoogleCodeExporter commented 9 years ago 
Never mind. Another browser relaunch, and all seems well.

Original comment by ken.mcgl...@gmail.com on 25 Apr 2014 at 10:17

GoogleCodeExporter commented 9 years ago 
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:15

GoogleCodeExporter commented 9 years ago 
I strongly believe this is the same as Issue 254

Original comment by nj.clare...@gmail.com on 26 Apr 2014 at 11:16