> Since you seem to be very knowledgeable

Nope, I just set breakpoints in Firebug to see the sequence

> http://www.geoffschultz.org/Test/infobubble_2.htmlutilizes an infoBubble

I think the infobubble 'domready' event is optimistic ; infobubble has
issued the commands to the browser to build the dom elements, but at
the time the browser is busy building map stuff and hasn't got around
to it by the time the infobubble code fires 'domready' in inline code.
In Firefox, there isn't even a map in the DOM let alone an infobubble
when your load_rotator() is called.

The standard infowindow runs asynchronously, and so gets queued behind
all the other map workings before its 'domready' is called.

I believe there is a trick you can do with javascript setTimeout to
put a task on the back of the browsers queue, use setTimeout to call
your load_rotator() with a zero timeout.

If this is the case, it looks like a worthwhile enhancement to the
infobubble library?

-- 
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.

Reply via email to