Hello Andy,
Both the examples are working perfectly well in firefox. There seems
to be some issue with the chrome. I would suggest you to post this same
query on Google Chrome support forum at
http://www.google.com/support/forum/p/Chrome?hl=en
Hope this help!
On Wed, Nov 17, 2010 at 11:20 AM, Andy Wismar <[email protected]> wrote:
> I've got a fairly typical "click map to set marker, click marker to get
> infoWindow" page thrown together, and I've come across some extremely
> strange behavior with the v3 maps API and Google Chrome.
>
> Here's the details:
> 1. Go to this page: http://wizmaps.appspot.com/static/index.html (you'll
> notice the points are already there, I've simplified the page as much as
> possible to demonstrate the problem)
> 2. Click around on the markers, you get a nice little infoWindow each
> time. However, once you click on the left-most marker (on Chapel Hill, NC)
> and close the infoWindow, the marker then refuses to give you the infowindow
> a second time. It's like the marker has lost the click handler entirely,
> you don't even get a cursor change hovering over the marker.
> 3. I have a second demo at http://wizmaps.appspot.com/static/index2.html,
> with different points but the exact same html/js otherwise. You'll see that
> clicking the leftmost marker doesn't do this handler-killing routine,
> *unless* you zoom in a few levels and push it towards the edge of the map
> boundary.
>
> I've been fighting this on and off for a few days, it's not always the
> left-most point, but one point seems to go bad and then all the rest of the
> markers eventually exhibit the same behavior after clicking around on them.
> This was just the set of points I had that could always reproduce the
> problem.
>
> Additionally, I've tried this extensively with IE 8 and FF 3.6, both of
> them work perfectly with no marker errors, but I can recreate the problem
> every time with Chrome 8.0.552.200 and the Chrome 9 dev channel releases.
>
> I've searched through the forums but didn't have any luck finding any
> similar cases, but this seemed like such a standard page that I'm sure I've
> got some nagging little problem in the JS that Chrome's picking out, hoping
> for help from the forum here.
>
> Thanks in advance,
> Andy
>
> --
> 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]<google-maps-js-api-v3%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-maps-js-api-v3?hl=en.
>
--
Regards,
Shreerang Patwardhan.
Trainee Developer
DSK Digital Technologies Pvt. Ltd. <http://www.dskdigital.com/>
LinkedIn Profile <http://in.linkedin.com/in/shreerangmohanpatwardhan/>
https://sites.google.com/site/shreerangmohanpatwardhan/
--
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.
