We have a problem on page where there is api v2 and v3 on the same page (api v3 being declared before the api v2 script). Prior to the update it was working correctly, but now we get an error with map.fitBounds(bounds) with the map api v3 object. Removing the api v2 script from the page fix the error, but have the side effect of removing all our v2 map =(
On a side note we also encounter the MarkerClusterer problem. A fix in the morning for you guys mean a fix at the end of the day in Europe and mean a full day of non working development code. We are aware v3 is still in beta, but it's the third time there is an update breaking things in previously working code. Is there a url parameter for the api v3 script to force a version to stck with v3.39 instead of 3.41 for us to be able to work in the wait of a fix? (markerclusterer is an easy one, but it migth be useful for future update. Thanks -- JP On 12 mai, 04:43, "Susannah (Google Employee)" <[email protected]> wrote: > We have just released a new version of the JS v3 API. If there are no > major issues, we will make a full announcement of this release in > 24-48 hours. Please report in the group if you see any regression > issues. > > Thanks, > Susannah > > -- > 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-maps-js-api-v3?hl=en. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
