Unfortunately I will not be able to make it, however there will be a funeral for IE6 on Thursday, March 4, 2010 at 7:00 p.m. in Forest Room 5, 2532 15th Street, Denver, CO 80211-3902.
For more information, visit the website at ie6funeral.com
In memory of IE6, here is a representation of how IE6 renders CSS
I ran into a strange issue today. I wrote a plugin for jQuery that used the load events from jQuery attached to an image. This plugin worked perfectly in Firefox, Safari, and Opera on PC, Mac, and Ubuntu. The only browser that it had problems with was IE.
I know. Completely unheard of right? I mean Internet Explorer is the best browser ever. Everything works perfectly in IE. (In case you didn’t catch that, that was sarcasm)
What the plugin was doing was creating an image element and adding it to the DOM. Once the image was added to the DOM I added the load event to it. The problem was that IE would only see the load event maybe 10% of the time at best. The only way I could get it to work in IE was add the image element to the DOM but don’t give it a src. Once the image element was added to the DOM, I created the load event listener. Once the load even was created, then I went back to the image and gave it an src.
This was an issue only on images with a smaller file size. The larger images didn’t seem to have as big of an issue with it except when I was testing locally. However, even the larger images weren’t consistently calling the load event.
Hopefully this helps out someone else. This drove me nuts for about an hour.
Microsoft has recently released Internet Explorer 8. It’s about time. IE7 came out a little under 3 years ago. They even made “Windows Internet Explorer 8: Get the facts” comparison chart where they say exactly why IE8 is so much better than the other browsers. It goes without saying that Microsoft pretty much got slammed for what they said in this comparison chart. I won’t go into it but you can read all of the verbal lashings they got on Digg.Even Webmonkey gave them a little bit of a lashing.
My question is, why? Why make that comparison chart? That chart won’t even be read my home users. And if they do read it, they won’t know what it means. The only people that will read it are developers that will of course rip it apart. So why would they want to set themselves up to be slaped in the face like that?
A lot of the comments are pretty funny. True, but also funny. They talk about IE’s slow Javascript engine, slow CSS engine, Favicons, developers tools, crash resistance and so much more. There were a few things I thought were funny. IE8 has full support for CSS 2.1, which is true for the most part. That’s great for Internet Explorer. But Firefox, Safari, and Chrome have been supporting it for around 2 years now. I even thought it was funny that HTML5 is rumored to be released later this year, will Microsoft have to go back to the drawing board with IE? Firefox won’t. They’ve already implemented a lot of HTML5. I believe Safari and Chrome has started as well.
After saying all of this, I do think you should download Internet Explorer 8 though. Even if you are on a Mac. I never said install it though. I downloaded IE8 on both of my Mac’s and my PC. I didn’t install it.
Microsoft has this thing going on where they will donate 8 meals to Feeding America for every download of Internet Explorer 8. You can read all about it here. So, please, download IE8. It’s a win-win situation. Microsoft get’s to boast about how many times IE8 was download (even though it wasn’t installed) and you make Microsoft donate 8 meals to feed the hungry.
[Update 12:49PM]: I just realized something. If you look at the source of “Windows Internet Explorer 8: Get the facts“, you will see IE specific hacks for IE7 and IE8. This contradicts their point on compatibility. Why would you need IE8 hacks if it is so compatible?
