[Google Maps API v3] Marker bounce has issues in chrome when cleartype is disabled
Hello, I've got a repeatable problem with the marker bounce animation in Google Chrome, when cleartype has been disabled. https://google-developers.appspot.com/maps/documentation/javascript/examples/marker-animations Is an excellent example. Disable cleartype (Start - Settings - Control Panel - Adjust ClearType Text - Uncheck the Turn on ClearType box) When viewing the above link in Google Chrome 19.0.1084.56 m on Windows 7 64-bit, watch the map credit text (lower right corner) carefully when clicking the marker to start and stop the bouncing animation. It fuzzes momentarily. In addition, clicking the start and stop the bouncing several times will eventually break the animation to the point that the marker will only bounce once when clicked, instead of bouncing forever. This problem isn't only aesthetic, because when the browser gets into this state, scroll windows stop responding to scroll changes until the mouse cursor is placed over the scrollable area. For an example on our application, please go to (in chrome, with cleartype disabled): http://tidesandcurrents.noaa.gov/map/index_bounce_problem.shtml?type=Active+Stationsregion=Virginia Mouse over to the scroll bar in the station list, and try dragging the scrollbar. The list will not update until you mouse over the station list. This behavior goes away if the marker bounce animation is removed from the application. Compare this behavior to: http://tidesandcurrents.noaa.gov/map/index.shtml?type=Active+Stationsregion=Virginia where the bounce behavior has been disabled for Google Chrome. Any help you can give would be greatly appreciated. -- 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/-/KIpiXDHiVqAJ. To post to this group, send email to google-maps-js-api-v3@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.
Re: [Google Maps API v3] Re: 2011/8/17 - New Release (3.6)
Sure. http://tidesandcurrents.noaa.gov/tsunami/index_markerproblem.html The only change I made was to remove the optimized: false parameters from any marker creation code. -- 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/-/n2oSquhk2OgJ. To post to this group, send email to google-maps-js-api-v3@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.
Re: [Google Maps API v3] Re: 2011/8/17 - New Release (3.6)
Keep in mind this problem only manifests in IE. -- 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/-/h_fRGRHafr4J. To post to this group, send email to google-maps-js-api-v3@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.
Re: [Google Maps API v3] Re: 2011/8/17 - New Release (3.6)
Thanks, and we'll do that, but why did this occur between 3.3 and 3.4? The frustration we feel is that we have many applications out there using this API, under an enterprise license. It would be nice if we could keep receiving a specific version when requesting it, instead of being inevitably upgraded as versions expire. -- 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/-/bdd_XZw1BVEJ. To post to this group, send email to google-maps-js-api-v3@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.
Re: [Google Maps API v3] Re: 2011/8/17 - New Release (3.6)
http://tidesandcurrents.noaa.gov/tsunami, although it's been changed to set optimized to false, because of the marker rendering error. -- 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/-/90tV3oY9KbIJ. To post to this group, send email to google-maps-js-api-v3@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.
Re: [Google Maps API v3] Re: 2011/8/17 - New Release (3.6)
Map markers in Internet Explorer broke. I've attached a picture. It happens for the standard map markers too. How would we have known to check for this in future versions? This is not the sort of thing you'd expect to break between versions, when it's been functioning fine for years (both under API v2 and v3). -- 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/-/lBXrVthWuREJ. To post to this group, send email to google-maps-js-api-v3@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. attachment: brokenmarkers.png
Re: [Google Maps API v3] Re: 2011/8/17 - New Release (3.6)
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 google-maps-js-api-v3@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.
