I’m developing a small Google Maps application and have come to hand over the first cut for testing. I don’t have a Windows machine about the house at the moment so didn’t test on Internet Explorer. The map going to be mostly used on mobiles anyway. Immediately the client told me that naturally, it didn’t work on IE. I managed to confirm this using browsershots.org and went looking for clues as to what the problem was.
The right path seemed to be that IE8’s security features can stop maps loading. This made some sense in Microsoft World as a page that was loading mixed data from different locations is probably Up To No Good, and the solution seemed to be to tell IE8 to act like IE7 in this case, using this header:
which naturally seems like the sort of horrible cludge that we have come to know and love from a web browser that is made by wage slaves in a cubicle farm in Bangalore.
The lesson learned: the world’s worst web browser can actually be quite helpful when it isn’t doing things that other web browsers do properly. Or when you’re trying to manage data without cleaning it.