[INVALID] Problem with Google Map Directions

[CoreyT]

This problem started a couple of weeks ago. The map in Google Map does not show the path from A to B. It just shows the A "pushpin". If I turn off ABE I see the path and the B pushpin. Has something changed with NoScript or Google Maps? How can I get Google Map directions to work properly without disabling ABE?

[dhouwn]

I am just guessing here because I have no idea what ABE would have to do with Google Maps but do you have the Google Earth plugin installed?

[Giorgio Maone]

Also, do you get any [ABE] message inside your Tools>Error Console?

[gryf]

Hi,

This problem started a couple of weeks ago. The map in Google Map does not show the path from A to B. It just shows the A "pushpin". If I turn off ABE I see the path and the B pushpin. Has something changed with NoScript or Google Maps? How can I get Google Map directions to work properly without disabling ABE?

I had the same problem with the directions offered by Google Maps, but it turned out to be caused by my having had set "geo.enabled" to "false" in about:config. Once I switched it to "true", the directions started working again (even though I denied access to my location).

I just double checked: NoScript's ABE setting has no influence on Google Maps's directions, regardless of what "geo.enabled" is set to.

CU

Thomas

[Tom T.]

I have geo.enabled = False, no Google plug-ins, no Google cookies allowed, and it works fine.

In addition to allowing, or temporarily allowing, maps.google.com, you must also allow or TA maps.gstatic.com.

I can break the site by forbidding gstatic.com, so perhaps this is the issue for you?

EDIT: I get the same results on Fx 7.01 as on 3.6.23.

Also, In both browsers, if you use the RequestPolicy add-on, as I do, you must allow requests from google.com to gstatic.com.

However, in Fx 7.01, the RP permissions are more finely grained, so additional destinations show. You must allow most of the things with "google" in the URL. Something like mt*.google etc.

Please let us know if this solves the issue for you.

[gryf]

Hi,

I just tried again with a newly created profile without any extensions and all plugins disabled: As soon as I set "geo.enabled" to "false", the directions at maps.google.de (or maps.google.com, for that matter) stop working. Switching the preference back to "true" makes them work again. Reproduced on both Windows 7 x64 Pro and Xubuntu 11.10.

CU

Thomas

[Tom T.]

I just tried again with a newly created profile without any extensions and all plugins disabled: As soon as I set "geo.enabled" to "false", the directions at maps.google.de (or maps.google.com, for that matter) stop working. Switching the preference back to "true" makes them work again. Reproduced on both Windows 7 x64 Pro and Xubuntu 11.10.

It seems to me that the only thing that would break by geo.enabled=False would be if you're using your own location as point A (or B). Then, they don't know your location.

If you enter two discrete points, it's hard to see how your present location matters. Have you tried, say, Berlin to Paris? Type in Berlin; if that's where you live, pick another city. Just don't use default location, 'Mein Standort".

I just did, on maps.google.com. It works fine. I then went to maps.google.de, temp-allowed the same two scripts, no cookies, and entered Dusseldorf to Frankfurt. No problem.

In RequestPolicy, one must allow requests from maps.google.de to google.com and gstatic.com.

Please try again. Danke.

[gryf]

Hi,

If you enter two discrete points, it's hard to see how your present location matters. Have you tried, say, Berlin to Paris? Type in Berlin; if that's where you live, pick another city. Just don't use default location, 'Mein Standort".

I just did, on maps.google.com. It works fine. I then went to maps.google.de, temp-allowed the same two scripts, no cookies, and entered Dusseldorf to Frankfurt. No problem.

In RequestPolicy, one must allow requests from maps.google.de to google.com and gstatic.com.

Please try again. Danke.

I was actually already using two discrete points (Heidelberg to Mannheim or vice versa, but it happens with any manually entered addresses), and since I was testing with a plain profile without any add-ons installed, RequestPolicy was not involved at all.

But since it definitely has nothing to do with NoScript, I suggest we leave it at that.

CU

Thomas

[Tom T.]

Oops...

Missed the significance of

I just tried again with a newly created profile without any extensions

-- that NoScript wasn't installed, either. So yes, it's not a NS issue, and will mark it as Invalid.

I suggest Firefox Help, or possibly a bug report if there's no information on it at Help.

Thanks for the report eliminating any NoScript issues.
Cheers - Tom.