Thanks for the detailed instructions - I can reproduce the error. My gut
reaction is that this is due to changes to hardware acceleration in Chrome
15 on Windows, but we'll definitely take a look.
Enoch
--
You received this message because you are subscribed to the Google Groups
"Google Maps
I'm seeing a Chrome regression with my delay issue (worked in Chrome
14), but unfortunately, cannot verify your flashing issue: Looks like
they're not related. Sorry -- I'll start a new thread.
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript
On Chrome Mac, I'm looping doing animated overlays by doing something
like
... newOverlay.setMap(map);
... prevOverlay.setMap(null);
prevOverlay = newOverlay;
I'm not seeing white flash, but I do see that it takes nearly a second
for the newOverlay.setMap(map) to "work", and the result is that the
I can verify the problem on Chrome 16.0.912.21 beta-m running on Windows 7
x64. It's a strange one!
I do notice that you're missing a "var map" - but adding it doesn't help. I
also tried one of those all-purpose hacks: wrapping the marker.setMap(map)
call inside a setTimeout - but even with a long
I am using Chrome 15.0.874.106 m on Windows 7 HP SP 1.
Many of my friends are able to reproduce this error. The error doesn't
happen on Chrome in Linux or Mac. It doesn't happen on Firefox.
*Also, you have to manually cut-and-paste the URL into a brand new
tab*.Clicking the above link won't sho
Which OS are you using?
Enoch
--
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/-/B7tzEYuKQS4J.
To post to this group, send email to
