IE8 issues

March 9th, 2008

By now we’ve all had a chance to try out IE8, and we’ve all found quirks, bugs, and pages that don’t quite work right. PPK has a summary of CSS issues. John Resig talks about JavaScript. Erik Arvidsson gives his impressions. I’m sure there’s plenty more out there.

I’ve found a few interesting things myself. Navigation on sites like Sourceforge and Codeplex doesn’t look right. MSN TV listings don’t work. But the biggest issues I’ve seen are with my raycaster.

Broken raycaster in IE8 - Cyberdemons everywhere

There are basically 3 causes of the problem: opacity, overflow, and zIndex. IE has never done opacity the same way as Firefox or other browsers; it uses filter: alpha(opacity=50) instead of opacity: 0.5. IE8 doesn’t seem to have any opacity support at all.

More noticable is overflow. I was using large spritemaps for the enemies, which were clipped to show a single sprite1. So the Sarge sprites are all in a single image file, and different parts of the image are shown for different individual sprites. In IE8, the images wouldn’t clip and the entire spritemap would be shown.

I made a CSS overflow test to pinpoint exactly what the problem is. I was using absolutely positioned imgs in a relatively positioned div. In Firefox and IE7, the children of relatively positioned elements are clipped, but not in IE8.

To fix it, I’m using a staticly positioned div for the container, and positioning all the content (walls, sprites, and sky) relatively.

The third problem is with z-index, for which I made a CSS z-index test. In IE7, there was no interleaving of children of siblings. So if 2 adjacent nodes, A and B, each have children with different z-indexes, there is no way for A’s children to be layered between B’s. Either all of A’s children are in front of B’s children, or they are all behind B’s children. And it all depends on A and B’s z-indexes, not their children’s. In Firefox and IE8 there can be interleaving if the z-indexes of the parents aren’t set. Also in IE8, there can be interleaving if the z-indexes of the parent are set to 0.

For more about IE8’s CSS handling, there’s the Windows Internet Explorer Testing Center and CSS Improvements in Internet Explorer 8.

  1. I did this so that only a few images needed to be downloaded. Instead of one for every frame and angle for each enemy, there is just a single image for each enemy type []

3 Responses to “IE8 issues”

  • TuX Blog » CSS con IE8 wrote:

    […] al problema opacità, sono stati riscontrati problemi con overflow e z-index, mentre Peter Paul Koch inizia la sua lista dei test preliminari su […]

  • Harry M wrote:

    I have started working in IE 8 and it seems to be more compliant (with a doctype and reset code) to FF than IE 7. I had to create a seperate CSS for IE 8 although it has reset some things to be more inline with FF. I had the !important hack on some areas to aid with IE7, 6. Although I have not gone too in depth in my research, the site we are about to launch needed minimal help to get IE 8 totally correct.

  • TL wrote:

    I consider IE8 a disaster it interprets CSS completely different from IE6,7 and Firefox everything needs to be reworked and I forsee this to be the case for many websites. IE8 is another bad joke from Redmont…

Leave a Reply

Name

Website

Comment