You may have already heard that a few of the most important CSS hacks are going to break in IE7. This is, in fact, a Good Thing™. What it basically means is that the IE team is getting its act together and trying to add as much standards compliance to IE7 as they can. All those child selector hacks we used to provide styles for non-IE browsers? Busted, since IE7 understands the child selector. On the good side, the browser finally does what it’s supposed to. And that’s what we wanted, right?
What it doesn’t mean, however, is that IE renders everything the way it should. We don’t know what will happen with those hacks. Will IE read them like Firefox, and then render them the same way? Doubtfully. If it did, the IE blog wouldn’t be sending out that call to action. In other words, we need to come up with alternatives to the current hacks. This could also mean going back to all those CSS websites we’ve done a while ago and replacing the hacks to ensure those sites work in IE7. Luckily, we’re all in the same boat, and to give us all a hand, position is everything has compiled a guide on how to work around those problems. Read it, you’re going to need it. With a browser of such major market share, there’s no way around it.