Originally Posted By: uc50ic4more
Originally Posted By: Nyquist
There are some pages you have to run in compatibility mode, but that is because the page is bending a rule or two on web standards.
?!?!?!?!?!?!?!?!?!
I know this has already been quoted in a reply, and I know it's been said before, but...
Internet Explorer is, by a long shot, the least standards compliant, least secure piece of garbage ever released on a commercial scale.
The only pages that bend rules and standards are the ones designed to function only with Internet Explorer, hence the necessity for IE to even *have* a "compatibility mode"!
Later versions are starting to suck a lot less than their predecessors in these regards, but it still sucks. The original responder had it right: They 1) embrace, 2) extend, and 3) extinguish standards, which 4) locks their users in to their proprietary suckiness, in an effort to 5) profit!
In the interest of disclosure, I have been using the beta in a virtual machine for a little while now; mostly to check sites I am working on, but also to evaluate as a browser, and I have yet to run across a site that "doesn't work" (If I did, I'd likely chalk it up to it being a beta...) My only quibbles remain, as they always have, related to the rendering engine.
IE 7 was the major offender of standards. IE 8 will try to undo that.
Just so that I'm not chalked up as a MS Kool-Aid lover, I have Red Hat Enterprise 5 on my machine as well. I've seen a lot of the same rendering defects on IE 8 and Firefox 3 (Windows and RHEL) at the same sites.
