Broken pages discussions part 2
If you use CSS hacks to work around standards compliance bugs, then the only thing I’ll say is that isn’t a good versioning strategy - but when you use them to work around issues that AREN’T related standards compliance issues then you are asking for that to break.
As for the other calls to “action”, well, perhaps I’ll respond to those on my own blog.
I did some google-ing on this some time ago. It appears that the idea has been suggested several times on CSS mailing lists, and systematically rejected (mainly on the ground that it would encourage browser-specific code).
I agree that aligning your standard-mode implementation on the consensus of other browsers would be a good idea. On the short term, it’ll avoid some problems for web developpers. On the longer term, it’ll allow a future standard to resolve the issue.
However, I’d like to point out that web page that rely on undefined behaviors are intrinsically broken. Maybe you can get IE to behave like Firefox or Opera, but it doesn’t mean that any standard compliant will behave in the same way. Designing Firefox-only websites is no better than IE-only. Moreover, in some other gray areas, there may not be a consensus between other web browsers.
