Comments on: IE8 opt-in: reaction from other browser makers http://www.broken-links.com/2008/01/23/ie8-opt-in-reaction-from-other-browser-makers/ Thoughts on web development and technologies by Peter Gasston Sun, 07 Mar 2010 16:33:42 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Peter http://www.broken-links.com/2008/01/23/ie8-opt-in-reaction-from-other-browser-makers/comment-page-1/#comment-6788 Peter Wed, 23 Jan 2008 14:05:16 +0000 http://www.broken-links.com/2008/01/23/ie8-opt-in-reaction-from-other-browser-makers/#comment-6788 My own hope is that the rendering engine of IE8 is so standards-compliant that we don't need to add any corrective styles to make up for it; that the only work we need to do is add the new META tag to our pages, and it will work perfectly across FF, Safari, IE & Opera. My own hope is that the rendering engine of IE8 is so standards-compliant that we don’t need to add any corrective styles to make up for it; that the only work we need to do is add the new META tag to our pages, and it will work perfectly across FF, Safari, IE & Opera.

]]> By: Dave Woods http://www.broken-links.com/2008/01/23/ie8-opt-in-reaction-from-other-browser-makers/comment-page-1/#comment-6787 Dave Woods Wed, 23 Jan 2008 14:01:53 +0000 http://www.broken-links.com/2008/01/23/ie8-opt-in-reaction-from-other-browser-makers/#comment-6787 It's taken a while for me to come to a decision on this. Initially, I was completely against it. Then when you start reading that the likes of Eric Meyer and Jeffrey Zeldman think that it could work, I started coming round to the idea, after all these people who have helped web standards to the stage they're at surely can't be wrong? However, after a lot of thought I've decided that I'm against the idea and you can read more about my thoughts on this here... http://www.dave-woods.co.uk/?p=153 But to summarize though, this change shouldn't really effect our day to day jobs in the slightest. My main concern is for those people that don't understand websites and who will be able to continue creating poor code that IE7 renders correctly even when IE9 and 10 are available because they're either unaware or don't care about the meta tag. Isn't this counter productive to what web standards is about? I've read it suggested elsewhere that the best thing to do when IE8 is released is to leave the meta tag out and render your website in IE8 as it would in IE7. We'll need to continue supporting IE7 anyway until all users have upgraded so why not just deal with one rendering engine where the bugs are already known instead of having to deal with two IE's. It’s taken a while for me to come to a decision on this. Initially, I was completely against it. Then when you start reading that the likes of Eric Meyer and Jeffrey Zeldman think that it could work, I started coming round to the idea, after all these people who have helped web standards to the stage they’re at surely can’t be wrong?

However, after a lot of thought I’ve decided that I’m against the idea and you can read more about my thoughts on this here…

http://www.dave-woods.co.uk/?p=153

But to summarize though, this change shouldn’t really effect our day to day jobs in the slightest. My main concern is for those people that don’t understand websites and who will be able to continue creating poor code that IE7 renders correctly even when IE9 and 10 are available because they’re either unaware or don’t care about the meta tag. Isn’t this counter productive to what web standards is about?

I’ve read it suggested elsewhere that the best thing to do when IE8 is released is to leave the meta tag out and render your website in IE8 as it would in IE7. We’ll need to continue supporting IE7 anyway until all users have upgraded so why not just deal with one rendering engine where the bugs are already known instead of having to deal with two IE’s.

]]>