This broke markers on two of our applications as well. If Google is going to constantly change the API, can it please do it in a way that ensures compatibility? The marker optimization is nice and all, but enabling, by default, a feature known to break marker rendering in IE? This is troubling. We can do without marker optimization, but we can't have our markers rendering incorrectly. Features like this should be disabled by default if they cause problems.
Lately, it feels like if we don't watch the API like a hawk, it will break our applications (we were requesting 3.3 and started receiving 3.4). -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/tZrZZ1DJMhUJ. 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.
