Quote:
Originally posted by JinSeung
Second -- they have tons of parsing errors, effectively making it a web designers nightmare, forcing you to either design your website around IE or having it display improperly in other browsers (or not display at all), in effect punishing them for their CORRECT working.
|
Com'on. Have you really done any web development for a client?
Some people might insist that simply coding standards-compliant pages would be enough. Standards compliant browsers would have no problems displaying your website then. This is ok if you're working on your own personal pages: you can tell your audience with impunity to go change their browsers. If they leave, it's their loss
. For business-related sites however, your audience wouldn't care. They leave and it's your client's loss. You've done your client a disservice.
Designing your websites around IE does NOT need to break compatibility across standards-compliant browsers. There's a ton of
hacks that a web developer could use to isolate some of their code to IE browsers only. Additionally, IE5+ has a
conditional comments feature, which you could use to isolate some of your HTML to IE browsers only.
Yes, IE is a web developer's nightmare. But as a responsible web developer, it is your responsibility to have your site work for
70+ percent of browsers out there! HOWEVER, the cardinal rule is: design your site around STANDARDS-COMPLIANT BROWSERS FIRST, then work around IE bugs. Where other web developers err is that they design around IE first, then when they try to make their site work with other browsers, sometimes they will find that it will take a lot of effort to fix their code.
Maybe in a perfect world, we could ignore IE. This is not that world.
