Hi Enoch, this seems to be related to GPU accelerated compositing (turned on by default with Chrome 15). Disabling it via command line switch fixes the problem, but that's not really an option with the end users of our google-maps-centered webapp (more so after urging them for months to switch to Chrome because it was way faster ...) Any hope of an update fixing this? (like, for example, a new chrome build disabling the bugged GPU acceleration?)
-- 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/-/HgxPS1T6eZgJ. 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.
