looking at what you posted in http://pastebin.com/m100c51f7 it appears that the extra code relates to timers and statistics. Perhaps google is measuring the load times of components, and occasionally during the development cycle of a new API version, this extra code appears.
However in an embedded IE browser there is already a window.external object http://msdn.microsoft.com/en-us/library/ms535246(VS.85).aspx this might cause a clash between the google test application which has it's own external object with a pageT (some kind of page timer?). I think the extra code is indended for some internal google timing measurments but is not compatible with IE7 embedded browser applications where window.external is "not implemented". What happens if you actually hook up the window.external to something in your hosting application? Then the first part of the if statement "if (window.external)" would return "true" instead of "not implemented", and the second part "if (window.external.pageT)" would return false. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
