Really about the only option is to have a second set of the images as gifs.
All the js workarounds suffer from some issues with certain types of images. (mainly related to css background images)
Correct. It is possible to do alpha-channel PNGs as foreground images in IE6, using a DirectX filter trick, but doing so causes terrible performance issues. It is not possible to do alpha-channel PNGs as backgrounds in IE6 without major scaling problems etc., not to mention the performance. It's far, far, far better to do GIF replacements for downlevel browsers. I went down the DirectX filter replacement trick road for a few years and it took months of development to undo that mistake.
I could probably just redo the skin with tables instead of divs and IE6 wouldn't have an issue with it, but didn't we all learn in webdev schools that tables are not for layout? :( But then again vBulletin uses tables too, so huh ..
Although the "web standards" guys would say don't use tables, in reality using tables can greatly help more browsers render your layout correctly. There are a large number of CSS "problems" in IE6 and other browsers that are fixed by using tables, thus eliminating any "hacks" and alternate stylesheets.
Oh, and btw, i've already spent a significant amount of time fixing the skin for various glitches in various browsers, and i can asure you, it DOES take alot more to get it working perfectly in IE6. But as i said, you're welcome to help
From what I saw of this site's state in IE6, it would take a great deal of work. Like Phanx said, the site needed to be built from the ground up for IE6 compatibility; most of the assumptions that were made need to be changed in order to work.
Why oh why would someone want to devote more time writing for IE6 than they spend writing for every other browser out there? I sure as hell won't!
I couldn't have put that better myself. The time it takes to make sure stuff works in IE6 is vastly more than any time I spend actually writing the code to begin with. It's fricking ridiculous. I curse IE6 every day.
there ya go, 90% of your web coding time spent for 6% of the users? NEVAR!
That's exactly the problem. IE6 really does take 90% of your time. It's a ridiculously bad browser. My point is, if they decide to support IE6, they clearly have a lot of work to do. If they don't want to support it, and they probably shouldn't given the percentage of hits they get, then no problem.
In the context of this web site, no support for IE6 makes sense. But in the real business world, where some of us make our money, IE6 is still there. If anyone wants to support it still, some of us can help. No need to be defensive. I say: forget IE6 for wowace.com. Just laugh at the screenshot.
Oh, wow. This site is pretty bad in IE6, looks like none of you have ever looked. Well, if it's really such a low user percentage, maybe you're fine. But if you did want to support IE6 you need to do a lot of work. Microsoft has a free VPC download containing a pre-activated copy of Windows with IE6 installed. Virtual PC is also free. You can test IE6 any time you want for free in this manner. I just keep the VPC paused so I can start it in about 3 seconds any time I need to do a quick test.
Here's a shot of how this thread looks in IE6. There isn't even a drop down next to the top Search link. The Search This Thread popup appears way off screen to the right.
According to this, IE6 still has 22.3% global browser share. For businesses, the percentage is much higher (I'd venture a guess of 50-80% right now). Luckily it seems this site in particular doesn't get many visits from it.
The dropdowns work in IE6, they just appear waaay over to the right. I noticed the horizontal scrollbar pop up when I clicked on one, and I found the menu hanging out half a screen's width to the right of the rest of the page content. So it's not a functionality issue, it's a positioning issue.
Without looking at it, it sounds like a CSS problem. These things are usually trivial to fix for someone who knows the ins and outs of IE6.
IE6 was first released over seven years ago (August 2001) and the last actual release was over four years ago (August 2004). IE7 has been available for about two years now, and most Windows users should have long since gotten it via the Automatic Update system. There is no excuse for anyone to still be using this grossly outdated browser with its abominable support for any form of web standards, and no excuse for web developers to hamstring themselves and their sites trying to maintain 100% compatibility with IE6 and other similarly ancient browsers (Netscape 4 anyone?). Thankfully, your response there seems to agree with my position.
Unfortunately, this is simply not enough of an argument for business users. In the huge majority of large IT departments, IE6 is still the official and only browser standard. Hell, one of my clients is only now switching their hospital over to Windows XP! And they think that's groundbreaking. Point is: IE6 is still very much alive and well if you have a web site that needs to be accessible to everyone. You simply cannot ignore it, much as I'd like to.
That being said, WowAce isn't a business related site, and I would have made the same decision and chosen not to support IE6.