On February 12, Microsoft will be pushing an automatic update to PCs far and wide that will transform Internet Explorer version 6 into version 7. The blogosphere is abuzz about how to avoid the update if you want to and is asking how Microsoft can tuck a software update into what should be security updates. That’s neither here nor there to me. Why folks would purposely avoid the update is outside my lane. I leave that to IT units at individual offices and agencies. I’m actually kind of psyched to see it; perhaps less cross-browser testing is on the horizon!

See, browsers are not like televisions. Different brands don’t all work the same. Imagine being a video producer and delivering your product to a broadcaster, then stopping by Circuit City for the big debut. Wouldn’t that be a surprise if one TV shifted the picture out of frame while another resized the image to bizarro dimensions, and a third finally displayed the video correctly. Well, you could just produce three versions of your show, right? One for each kind of TV. That’d be a hoot. We may not have to generate completely separate products, but web developers do wrestle with a similar scenario.

Despite the best efforts of organizations like the WC3, browsers just don’t all work the same way. They don’t display content the same way. Pieces move or resize or disappear completely. Depending on the goals of your organization, those differences can have large impact.

The latest stats show Internet Explorer 7 holding 21 percent of the market. IE6 holds 33 percent, Firefox 36 percent, and then a steep drop down to Safari, Mozilla, and Opera. Notice the name Netscape isn’t even tracked anymore! Depending on your goals and audience, you may need to test your websites/applications on all of those browsers (not to mention platforms like Mac or PC) to make sure everyone is seeing the same thing and enjoying the same experience.

So how do you decide how much time and effort to put into cross-browser and platform testing? That depends on what you’re doing. If you’re facing a closed audience with predictable systems, you may be able to cut down on testing. For example, a DoD agency targeting an internal audience can feel pretty good about things as long as they’re targeting Internet Explorer 6 (until Feb 12?) and Windows XP. Meanwhile, that same agency may have a public-facing website, one offering critical information or training, one that could reflect on their image and mission. In that case, how accommodating should it be? Is it OK to serve up content that may look wacky on a Mac because it holds such a small share of the market? I’m happy to say that’s not my call. But I could help you think through it. And would you believe it comes down to time and money? I know you’ve never heard that before.

I will say this: There are standards out there, and if we stick to those when building, our chances for success are good from square one. Further that, simply having the experience and awareness of cross-browser/platform issues is another big advantage. Finally, it’s about paying attention your audience and making educated decisions. My decision would be to dump IE6. One version of that browser is enough for all of us.