Archive of: markup
We’ve decided that IE8 will, by default, interpret web content in the most standards compliant way it can. This decision is a change from what we’ve posted previously.
- Dean Hachamovitch on the IEBlog
This is great news, kudos to the Microsoft team for listening to the community and changing their approach.
(for more background see Jeremy Keith and Jeffery Zeldman’s articles in issue 253 of A List Apart)
Ben Henick has a new article over on ALA: 12 Lessons for Those Afraid of CSS and Standards. There are some great tips and hints here for those of you starting in web development, or those who are trying to break some bad habits gained over the years.
This one struck a particular chord with me, as it’s something I’ve been trying to explain to clients for a while now:
Lesson No. 2: It’s not going to look exactly the same everywhere unless you’re willing to face some grief… and possibly not even then
There are an awful lot of differences between rendering engines, and the W3C specs sanction those differences. You can adjust, tweak, hack, and waive, but if you want to preserve your social life, you will learn to let go of the small differences—and convince the stakeholders in your projects to do the same.
Amen to that!
While Microsoft may pay lip service to web standards, a look at their product line suggests they have no interest in supporting the standards theyâ€™ve helped create. Face it, xHTML and CSS just arenâ€™t as sexy as .Net and web services. Microsoft clearly has other priorities and a closer investigation of the facts seems to indicate that support for web standards is hardly a blip on their corporate radar.
This is an extrememly well written piece that should give all of us pause for thought, and with any luck may prompt increased pressure on Microsoft to make standards an intergral part of their offerings.
I’m now off to code up some workarounds for IE5.