Hi Barry, I tried out your suggestion by running two of the frozen versions 3.2 and 3.3, but both of them produce the same result. When I looked at that thread you posted, they mentioned it was removed for Markers. I'm using KML Layers in this case which is probably different. Your explanation seems logical to me though, but I don't know much about DOM events so I can't say for sure if that is actually the reason.
@Larry: I thought I replied to you about your response. I wonder why it hasn't been displayed yet... Thanks guys, Tony On Apr 8, 5:44 am, Barry Hunter <barrybhun...@gmail.com> wrote: > On 7 April 2011 17:16, Tony <ton.anh...@gmail.com> wrote: > > > > > Does this happen because the user's browser doesn't detect that the > > popup is "user initiated"? > > I would think so. See this thread: > > http://groups.google.com/group/google-maps-js-api-v3/browse_thread/th... > > As the Maps API, bypasses using DOM events, it quite possibly means > the popup blocker just sees the window.open initiated via javascript. > > ... > > Firstly I would suggest trying a earlier version of the Maps > APIhttp://code.google.com/apis/maps/documentation/javascript/basics.html... > > And IF it works there (because it still used DOM events), then jump on > the linked thread, to let Google know of a use case for using real DOM > events. -- 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 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.
