I'm generally very pleased with the v3 API. I have my entire site converted over from Maps API v2, and it's working well. The site seems to load faster and is more responsive.
The one area where I'm a bit frustrated is the handling of click events. When a user double clicks on the map, they want to zoom in. Why does a map click event fire? That just doesn't make sense. Clicking on the map is different user action than double clicking. And the fact that the click event happens before the doubleclick event means that I can't even stop the click event. Equally messed up is the handling of polygon/line clicks: http://code.google.com/p/gmaps-api-issues/issues/detail?id=2172 Any idea when these will be fixed? Also, when will versioning ala v2 get implemented? I want to roll out to production, but with v2 I've had to pin to older versions a few times due to regressions. For anybody interested, I run a flight planning site for recreational/ small business pilots. I'm fully invested in Google APIs with Maps, Adsense, Google Closure library/compiler/templates and soon local search. The main site (www.runwayfinder.com) is still using Maps v2, but the beta is on Maps v3 at www.betarunwayfinder.com. Dave -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
