I see this problem has been posted before but I don't see an answer.
Map appearing in Windows IE7 and Firefox and in my Mac browsers but a
blank map in IE6 (the address shows in the address box and there is a
grey box where the map should be).
I can confirm the grey background IE6, for what its worth.
Struggling to read the JS so can't help much, but noted you're
geocoding the address for every site visitor. Assuming the store
doesn't move around much, why not just plonk the marker at a fixed lat/
long and eliminate the vagaries of asynschronous geocoding?
On Apr 14, 10:40 pm, ruthie <r...@lipserve.com> wrote:
> I see this problem has been posted before but I don't see an answer.
> Map appearing in Windows IE7 and Firefox and in my Mac browsers but a
> blank map in IE6 (the address shows in the address box and there is a
> grey box where the map should be).
You're not using the bog-standard Maps API, but an add-on set of
"helper" functions, which is making debugging difficult. However, I
can see that there's a <body onload="load()"> but I can't find a
function called "load". There's a cmxMap.load(), which is already
called as part of cmxMap.js.
Firefox and IE6 tend to handle errors differently: Firefox will carry
on executing code if it can, whereas IE6 tends just to stop dead.
(I've no idea about IE7, as I don't run it, but it looks like it
behaves like Firefox.) I suspect this is what's happening here:
Firefox is encountering the "Can't find function load()" error but
it's not fatal, so the function cmxMap.load() carries on running and
you get a map; IE6 just stops *all* Javascript operations, so the API
is prevented from downloading map tiles, having got as far as setting
up the map.
All that's a bit of a guess, admittedly. What happens if you take out
the onload attribute from your body tag?
Andrew
PS: Rossko is right about geocoding. The store isn't going to move.
This is a bit of code that only gets loaded when the browser is MSIE6. It searches through the DOM and attempts to "fix" any PNG files that are used on your page. The problem is that the API displays PNG files correctly in the first place, and when iepngfix attempts to "fix" images that don't need fixing it completely breaks them.
You can't use iepngfix on pages that use the API. Since there's only one "unfixed" png file on that page, you could just write your own Javascript to call the AlphaImageLoader on your logo.png file rather than have iepngfix modify every png image.
|
