On Jun 24, 5:07 pm, Donovan Walker <[email protected]> wrote: > Nice reasoning. I've added a couple more examples, and will report > this as a bug.
Yes, that has to be the next step. > Examples have been updated with descriptive > text.http://dev.y2g.org/?page=preDOMhttp://dev.y2g.org/?page=postDOMhttp://dev.y2g.org/?page=postDOM_1http://dev.y2g.org/?page=postDOM_2 Example 2 hangs as documented here with the <body> element destroyed, but so does 4 in FF3. I don't think this particular bug is perhaps too devastating for an error message or exception to cope with. > A summary of 'how to fix' right now would be... if you're going to > call google.load('maps'.... > you MUST specify a 'callback' in your options param like > > google.load('maps', '2', {callback:/*functionname*/}); > > as long as callback is present (doesn't even need to be a function, I > assigned {} in a test) the DOM isn't destroyed. For form's sake if one > is not going to do an actualy callback function I suggest using an > empty anonymous one .. > > google.load('maps', '2', {callback:function(){}}); Yes, that seems to be a good fix, but the bottom line is that whatever is destroying the <body> element has absolutely no business to be doing so, and should be fixed asap, by which I mean preferably 'yesterday'! > Thanks Marcelo, JavaJ, Rossko. Seconded, but most of all to you. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
