Broken pages discussions part 1
As a CSS developer I’m well aware of which hacks I’ve used where and why, and as far as I can tell nothing will break with the arrival of IE7.
I presume this post is a preemptive strike so that IE’s critics won’t be able to say “IE 7 Launched; Internet Breaks”. But if you’ve done what you say you’ve done this won’t happen. I’m very pleased that the ‘* html’ hack has been removed ‘casue all my pages would go bad without it. What you seem to be saying here, though, is: “we haven’t quite fixed the layout, so you need to check out other ways of hacking IE”. Before we’ve even seen it.
I trully believe you ought to consider bringing forward the release of Beta 2 - even if it’s only Beta 1 with the CSS changes (and slate a Beta 3 relase for December with the other stuff). I can’t be the only one who wants to check my sites in IE7, but none of us are going to rewrite a single line of CSS til we’ve seen it.
I know it’s not an ‘ie-hack’ but it’s a bit of a hack anyway and it standards compliant browsers it relies greatly or proper parsing and implementation of css’ :after and the IE hack side of it relies on IE’s incorrect box model always expanding to enclose floated contents.
I think a number of you are missing the point. The problem, as I see it, is that many web designers have gone and used particular hacks to hide or show rules for IE, when the hack is a totally separate symptom unrelated to the issue they’re trying to work around.
It’s fine to work around bugs in a specific version of IE - but you’re not versioning that or allowing us to not break your content while moving our standards compliance forward.
