The problem at this point looks like this:
- it only happens in the Firefox 4 browser. Other browsers like IE 8 & 9, Chrome, Safari, Opera and Firefox 3.6 don't have this problem.
Since the page where I saw the error belonged to a web application I started working on, I had to fix the problem. An initial search on the Internet did not bring up anything useful except that a few other people also stepped on this problem. I tried Bing Maps' interactive SDK and it worked all right. That told me the Bing Maps script itself does work but it clearly depends on some other condition that does not necessarily happen on other pages like mine.
attachEvent function that caused the error and must be loaded first before the main Bing Maps script. So that's the condition I've been looking for! Now the picture got clearer:
- it only happens in the Firefox 4 browser. Other browsers like IE 8 & 9, Chrome, Safari, Opera and Firefox 3.6 don't produce that problem;
- it happens when atlascompat.js is not present on a page at the moment when the main Bing Maps script is being loaded.
Now why is the error happening on my page and not on the Bing Maps SDK page? Apparently the condition #3 is not satisfied since my page contains a whole bunch of other scripts and the atlascompat.js did not load before the main Bing Maps script due to internal differences that have been introduced in Firefox 4. Now I have a complete picture of the problem and can come up with a solution for it.
The solution is simple: since the Bing Maps itself cannot load the atlascompat.js reliably, I need to help it and just add a reference to the atlascompat.js script on my page before a reference to the main Bing Maps script. This can be easily accomplished with a few line of code, like below:
if ((Page.Request.Browser.Browser.IndexOf("Firefox") >= 0) &&
(Page.Request.Browser.MajorVersion == 4))
In my case, I added the code above into a
GetScriptReferences method of an
IScriptControl that was responsible for rendering the Bing Maps on the page.