On 04/01/2011 04:04 PM, [email protected] wrote: > I thought I had seen threads that implied the .ready event happens > before the document.onload event (but I don't use it). I also thought > that the end result of those threads was running the map > initialization in the document.onload event solved the problems.
Thanks! I'm not sure whether '$(document).ready()' fires before or after 'document.onload()': it shouldn't matter for my app, as the only thing I do inside '$(document).ready()' is bind the JS API functions to the corresponding 'pageload' events. The UI model here is based on one big HTML page with a top-level div per "viewable section": the event which triggers it is showing the "page" div which contains the map canvas div. I've stepped through the code in the Chromium and Firefox browsers -- it is definitely running long after the page has done loading. The canvas node is present, and stays light green until after the map code scribbles on it, at which point it turns gray. In the DOM inspector, the element has leaf-level style changing its color, which overrides the CSS rule set at document scope: I assume that means that the Google API code has mutated it directly. Tres. -- =================================================================== Tres Seaver +1 540-429-0999 [email protected] Palladion Software "Excellence by Design" http://palladion.com -- 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.
