InformAction Forums

Have been using NoScript for several weeks, and Google Maps has been working fine throughout that time.

This morning I tried to search for a location in Google Maps and got a "Still Loading..." message but otherwise no response. When I traced down the 'Troubleshooting' link in Google Maps, and after trying some 'about:config' adjustments they suggested to no effect, I disabled NoScript...and everything works just fine again.

What could have changed to cause this to happen? (And how can I get NoScript running again w/o interfering w/ Google Maps?)

Usually all you need for Google maps to work is google.com (and possibly the local site for your country, e.g. google.de or google.co.uk, N/A in US).
Maybe something got corrupted in your configuration, and you may want to try #1 at http://forums.informaction.com/viewtopi ... 1431#p4767

Thanks for your suggestion, Giorgio...but this did not fix the problem.

However, I looked closer and found something that I carelessly missed the first time; apparently Google Maps has added scripts from a new domain: gstatic.com

I guess I've come to expect (depend on) the 'NoScript bar' across the bottom of the the browser to warn me when one or more script domains is being blocked; for some reason this does not show up on Google Maps, and I failed to notice the small 'blocked' symbol on the NoScript 'S' icon in the lower right.

My bad.

thanks, to both of you. Can't imagine how I missed adding this gstatic.com link in the maps.google.com display but I managed to (surprisingly on one computer but not the other). with your tip I managed to get that cleared.

jvlb@charter.net

Thanks Bill, I guess I'll have to add this gstatic.com domain to the default whitelist.
It should be as "safe" as google.com (which is there for convenience), if not more: in facts, judging by the name, it should not export any dynamically generated content.

Part of the reason I run NoScript is that I want to have some idea as to who is running what before I would authorize. I certainly would not want to put gstatic on the whitelist with the assumption that all is good for every possible time that gstatic would be involved. Do you know where else it is run and why? I don't even know what new benefit it provides me with Google Maps. Because it is a surprise and gives no obvious attempt to say it is a new script that has not been authorized yet, it does raise a red flag.

As the name implies, it's probably used by Google to offload static (non DB-generated) resources, such as images, stylesheets and JavaScript files.
If you want it to run from google maps only, you can add the following rule to your ABE "USER" ruleset: