I, Too, Want to Kill IE

Posted in kaMap | Saturday, June 2nd, 2007 | Trackback

We’ve been using kaMap on top of for a couple of different things, and the first one out the door is a scanned/rectified collection of 1929 orthos of a decent segment of the Wabash River. Problem is, it looks very nice in every browser but Internet Explorer (pick your version). This is a legendary problem, of course, but…it still bites it. I was able to solve part of the problem illustrated below by choosing a much thicker font, but the little png markers are still rendered as jagged little icons rather than shadowed images. I’m not a web developer, but I don’t see how people who develop for the web can stand having to account for ie users. That app presents a ghastly, retro view of the world and I don’t like it. To wit…

ie kamap renderfirefox on windows renders kamapomniweb renders kamapopera on mac renders kamapcamino renders kamapsafari renders kamap

3 Responses to “I, Too, Want to Kill IE”

  1. andrea Says:
    June 2nd, 2007 at 1:05 pm

    hi,
    probably you have just the solution. I have solved png problem with this:
    http://homepage.ntlworld.com/bobosola/pngtest.htm

    regards,

    a

  2. Morten Says:
    June 2nd, 2007 at 7:52 pm

    Not much point in ranting. To be fair, maybe you should try it in IE7. It’s a known problem, and has been resolved.
    Btw. do you use the IE6 png workaround? You can apply a filter in IE6 that solves many of these transparent PNG issues.

  3. geolibro Says:
    June 2nd, 2007 at 8:31 pm

    I have used bobosola’s fix before, yeah. It did work on regular pngs. The other one I’m using on pngs in regular web pages is koivi’s replacepngtags.php, which also works very well. But ka-Map is already doing this, from what I understand. Otherwise there wouldn’t be any transparency at all, let alone transparency that looks rough. In other words, the entire map would be hidden behind the non-transparent pngs of the top-most map layer. I think. Anybody well-versed in kaMap know if that’s right?
    And there was a css filter fix for this as well, I remember, but for some reason I don’t recall I couldn’t get it working.
    And you’re right about IE7 (though I’ll never be convinced that it looks “good”). My problem is that a decent portion of the users of this particular map won’t be using IE7. It’s hard to believe, but that ie6 market share just isn’t going down fast enough.

Leave a Reply