There’s no question that Internet Explorer 6 has replaced Netscape 4 as the most reviled browser known to Web development. Just do a quick real-time search to see how Web designers feel.

There’s a lot not to like. To name just a few short-comings:

• It doesn’t render the transparency of Portable Network Graphics (*.PNG files) properly, requiring a browser-specific filter
• It doesn’t render a lot of the latest CSS declarations

(I could go on and on, but why relive the agony?)

This means that Web designers need to invest extra time making sure IE6 renders their creations properly, and that makes us, um… cranky, and rightly so.

Some designers actually seem to be personally offended by people who use IE6, and want to force them to switch browsers by denying them access to their Web sites if they use IE6.

This approach is miguided and does not take into account the fact that many people cannot upgrade because they access the Web from corporate IT environments that only support IE6.

Other designers are bewildered that some people would continue to use IE6 when other options exist. The reason has to do with usability, and is best characterized by the phrase “if-it-ain’t-broke-don’t-fix-it”. In other words, people who use IE6, many of whom are non-technical, get along just fine, thank you, sending email and surfing and purchasing with adequate security. These folks have no incentive to switch.

It’s hard to get angry with people for that.

Designer Andy Clarke recently considered the options regarding the IE6 question and proposed a Universal Internet Explorer 6 CSS file as a solution. Basically, Clarke, says, serve up a plain jane style sheet that allows folks with IE6 to view a Web page’s content, but conveys the message that their browser is not up to par in terms of rendering its layout.

Some top flight designers have adopted this approach, as Jina Bolton did recently when she redesigned her personal site, Sushi and Robots. UIE6 has popped up on a couple of sites here in the Portland area as well.

So, has the time come to employ the Universal Internet Explorer 6 CSS more routinely? The answer depends on the audience for your site as well as its content.

A quick spot check of W3Schools browser stats suggests that roughly 10% of all Internet users view it through IE6 (about 4% of the visitors to this site use IE6).

If your site caters to the general public and traffic analytics show one in ten visitors are using IE6, I’d say the time has not yet come for you to switch. You’re still better off employing progressive enhancement techniques in your CSS to serve up a design that still looks sharp, if not a pixel-perfect clone of what’s seen in other browsers.

If 4% or less are using IE6, and you’re not conducting any e-commerce, I’d say you’re safe giving UIE6 CSS a spin.

But if you do use UIE6 CSS, make sure you check to see that things are rendering properly. Sometimes goodies like jQuery, bereft of the CSS used in other browsers, leave the interface looking a little messy and content unreadable. Yep, I’ve seen that on at least one local site-that-shall-remain-nameless.

Remember, IE6 users are people too. They deserve a great (if not pixel-perfect) user experience like everybody else.

Next week we’ll be talking about Pemaquid’s current approach to handling CSS for IE6.

Have any of you out there used UIE6 CSS? Let us know how in the comments.

I downloaded Chrome last night and ran pemaquid.com and several other sites that apply Web Standards through it, and they all checked out, even the features fortified w/(Progressively Enhanced) Ajax.

Separately, a CSS bug has been reported by Jeremy Jarratt, in that Google Chrome improperly displays alternate style sheets. This is apparently a bug that has existed in Webkit and Safari for some time. (information via Jeffrey Zeldman).

Because of Google’s high profile, Chrome could have more of an immediate impact than Firefox did when it came on the scene. I’m hoping that’s going to be a good thing.

For example, it might wake up certain IE6-centric developers slumbering blissfully ignorant to the existence of Web Standard design principles, when they wonder why their sites don’t render consistently in a suddenly-popular Chrome.

Still, it remains to be seen if Google Chrome will make a sizeable dent in the browser market. As we’ve seen with the continuing significant market share held by IE6, people don’t easily switch browsers unless they find it compelling to do so.

One thing’s for sure, as Zeldman says, we once again live in interesting times regarding Web Standards, Web content and Web browsers.

Reports say Google intends to release the browser for download from its site today at: google.com/chrome but so far nothing’s available.

I haven’t had time to immerse myself the details yet, but here are some of the important details:

• It will be open source
• It will offer a way for people to see how Web sites are consuming system resources
• It will handle tabbed browsing in a slightly different way

This could have a major impact on both Microsoft’s Internet Explorer browser as well as the Mozilla Project’s Firefox.

You can find out more about the Google Chrome features at Google Blogscoped, a blog which follows the company; learn more about some of the technical implications of Google Chrome from John Resig on his blog.

As far as the impact on front end Web designers? It remains to be seen, but if you assume that Chrome adheres to Web standards and standard CSS implementations, it shouldn’t change the game all that much. Stay tuned….