Bear in mind the API is effectively issuing instructions asynchronously to the browser to create the elements ; the work is queued and takes time to do. Hence even a setTimeout of 0 can apparently effect the order of events, since that goes on the end of the browser's queue, rather than the currently executing code hogging resources and locking out other things in the queue (like actually rendering the infowindow).
There's nothing to stop you creating custom infowindow-equivalent code, if you don't like the way Google's is optimized (which seems to be more about the user seeing things happen onscreen, than strictly sequential working) -- 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.
