Broken pages discussions part 4
It seems to me that, if the new browser IS in fact standards compliant, then the hacks will just pass them by, as they do Safari, Firefox and the other compliant browsers.
I don’t think I’m going to ‘de-hack’ anything until Microsoft lets us know that, say, 90% of their users have migrated to the new browser. After all, the whole point behind the hacks was to make the CSS work for the 90% of the audience who were using a non-compliant browser.
To me, I think my life is become more troublesome now that there are no longer any techniques to treat each browser differently.
It is understood among the majority that the way pages are rendered depends on the browser. I see in Firefox I must specify a height in a div tag that has another (set of) div tag(s) with content in it or else the div tag border shrinks to the smallest height possible (which is not encompassing all that lies inside).
To me, the hacks were not exactly hacks and the bugs were not bugs. It was part of the way browsers worked. If rendering of every browser is not the same, then each browser should have a unique code to it.
You all should look into going all-CSS. The web community has made a lot of advances in the past 10 years. It’s great that Microsoft is going to help us out again. Unfortunately IE fell off the priorities list after Netscape was crushed. Happily, IE seems to be a priority again, and we’ll be able to do even more cool stuff with CSS.
