Clicking First Step in Directions Renderer Zooms to Random Location

51 views
Skip to first unread message

Justin Ingram

unread,
Jul 18, 2011, 9:25:18 AM7/18/11
to google-map...@googlegroups.com
Hello, I'm having an issue with the V3 Google Maps API Directions Panel. Directions are loaded correctly on the map as well as in the directions panel, however clicking one of the directions in the panel causes unexpected behavior. The first one of the steps clicked will zoom the map to a random location, but clicking a different step afterwards works correctly and then everything works as normal. I'm currently working on another website, but I discovered the issue on one of my previous uses of Google Maps:
http://www.leehighgenerals.com/leehighdocs/map_beta.html

The issue appears in every browser I have tested using my code.

The page uses a compressed version of the javascript, but you can find the uncompressed one at:
http://www.leehighgenerals.com/js/directions.js

I'm currently using similar code to develop a maps application for a radio station using jQuery 1.6.2 and the problem is persisting. I found where someone had a similar issue here: http://stackoverflow.com/questions/6482474/google-maps-api-v3-directions-clicking-first-step-bug

Any help to resolve this issue would be greatly appreciated. I currently do not have access to a server to show an example of the code I am working on now, but the issue appears to be the same on both maps. I should have the server for the new website running later this week, and I can post a link then, however, the issue is well demonstrated on the link I posted.

Many thanks.

Justin Ingram

unread,
Jul 19, 2011, 10:34:11 AM7/19/11
to google-map...@googlegroups.com
Additionally, the problem can be seen here:
http://leectysch.com/web/mapfinal.html

and here:
http://leectysch.com/VT/web/map.html

These two websites use basically the same javascript, and have the same issue.

Justin Ingram

unread,
Jul 19, 2011, 12:09:47 PM7/19/11
to google-map...@googlegroups.com
I have found the issue: changing to loading version 3.4 of the maps api instead of the latest resolves the issue. Perhaps this should be entered into the bug tracker.
Reply all
Reply to author
Forward
0 new messages