Quote:
|
Originally Posted by aicul You are right, IE is a miserable thing to deal with when building sites, but unfortunately you have to live with it.
I have a slightly different approach from you, I regularly use IE. So when my newly developped site works on this piece of C##@R@##A#&%P software, I'm sure it'll work on professionally developped browsers. |
Don't be so sure of that.
Microsoft regularly invents HTML properties and objects (see Frames [iFrames, frameborder etc], scrollbar colouring, directX alpha shading and ActiveX) and it's up to the W3C to decide what makes it through into ratified standards (which standards-compliant browsers comply to, funnily enough).
The problem is, they're implemented in IE (and that abomination called FrontPage), so stupid, stupid, RIDICULOUSLY IDIOTIC web designers use them and it makes Firefox, Safari, Konqueror etc all look underpowered and unuseful.
IE is *the* reason why I feel Microsoft is so hated in the open-source community (which is almost entirely standards-based). Its flagrant ignorance of the established standards bodies in place (starting with the lack of JVM in XP, all the way through to their apparent hatred of the W3C). Rumour had it that IE7 will fix that for us all, but MS has said that they won't ever release another standalone web browser. Meaning maybe IE7 won't be released on XP, 2K, Me, NT or 9x.
Meaning we'll all still be writing to those pretend standards that IE 6 and 5 set up.
I just wish when they have problems they'd either FIX them, or LEAVE them, so you could have expectable behaviour every time.
Edit:
The worst part is, the unpredictable behaviour of IE when rendering standards-compliant code leaves people consistently writing TABLE-BASED layouts. Which stops forward advancement of the medium.
I admit, there're holes in the standards at the moment (no vertical-alignment is the glaring one), but the longer people are forced to learn tables as a layout technique, the longer it will take IE to change. It's a horribly vicious cycle.