The order of things being ready is pretty variable, not just on browser but on network traffic, latency and all kinds of factors.
It's sort of assumed we're working in a messy environment. :) To deal with that, one's best course of action is to check when things are ready (like you're doing now) and only fire dependent stuff when what you need is loaded. :) check the source files of dev.y2g.org?page=map for a working example. G'luck! On Jun 25, 7:25 pm, JavaJive <[email protected]> wrote: > Yes, another error, got it working now. > > Interestingly, I've now added lines to track the order in which things > load, and, as I noted in the issue report, it's different in different > browsers. This means that one cannot assume any given order in all > browsers, hence the juggling with the *Ready variables should perhaps > be standard coding, and therefore documented as such? > > FF3: > Google AJAX API Ready > DOM Ready > Google Map API Ready > > IE6: > DOM Ready > Google AJAX API Ready > Google Map API Ready > > Opera 9: > Google AJAX API Ready > DOM Ready > Google Map API Ready > > On Jun 26, 12:52 am, JavaJive <[email protected]> wrote: > > > Ah, I see I got the google.load syntax wrong! > > > Correcting that I have a blank div, the map is still not loading, BUT > > the <body> element has not been destroyed, so maybe I can now figure > > out why the map didn't load, which presumably must be a second error. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
