MS Urging Developers To Prep For IE 7
Mike Savior writes "Eweek has a story stating that Microsoft is telling web site developers to prepare their sites for IE 7. From the article: 'One area that Microsoft has clearly articulated as being one in which developers can start work now to prepare for IE 7 involves the UA (user agent) string. First discussed in the company's Weblog in April, the code change prompted a reminder on Wednesday to developers, telling them that Microsoft continues to run across Web sites that are not expecting Version 7 of the browser, and urging them to test their UA strings. '"
If you are depending on the user agent string, your web site design is flawed already.
Sure IE is broken... but you just have to format to fit the lowest common denominator.
Trying to detect the browser type for the majority of web designers is just silly.
"I don't use IE at all, but I'll test on it because I have to," said Web designer Donna Donohue, owner of Norwich, Conn.-based development firm KidoImages. "We code to standards to be compliant with Firefox, and then hack for IE."
Same for me. Our website uses standard CSS and it needs a hack (csshover.htc) to make it work on IE. Maybe IE7 no longer requires it, maybe it does. Who knows?
Until then, the conditional stylesheet inclusion for IE has to remain there.
"Coding for all browsers is expensive and increases our development and support costs".
That's the BS I usually hear from people who develop only for one browser - typically the "corporate standard" browser.
No, it's true. Try developing a website using CSS 2. It'll work in Firefox, Opera, Konqueror and Safari just fine. Now check it in Internet Explorer. Whoops!
If you want your website to work in all browsers, then you have to either forget about CSS 2 (meaning slower development) or hack around Internet Explorer's problems (meaning slower development). Slower development == costs more.
How many tutorials have you seen with different methods of achieving multiple column layouts? Did you know that you just need a couple of lines of code to do it (display:table-cell etc) in all the major browsers except Internet Explorer?
We have a very small software development staff. As the manager of this organization, I can say with confidence that supporting all browsers versus just one costs us zero dollars.
I'm in a similar situation, and I can say with confidence that Internet Explorer slows us down, which costs us money. Coding to standards is not the same thing as making it work in all browsers.