IE8 and versioning – very worrying developments

I am not a fan of targeting browser versions. Nor am I a fan of the “opt-out” proposal. I am also unhappy about the idea about going back and adding a new meta element to every site I have done. It seems many others aren’t happy either. I’ve been collecting links for the last couple of days. Here is some articles and comments on the subject

Date: 24 January 2008
Author: Russ Weakley
Category: News, Web, Web standards

Comments so far

  1. Question: What will happen if we do NOT add the infamous line to our websites??

    From my (limit) understanding, it wont change anything but just want allow the new stuff to be used.

  2. Russ,

    I couldn’t agree with you more, this is very worrying. I read the article in A List Apart suggesting this, and it gave me flashbacks to 1996, where targeting browsers was all the rage!

  3. Gary Barber says:

    Yes its a bad thing in a way.

    But no one has considered WHY this has happened. Think about it.

    The web community has been making noise on standards compliance.

    Sure MS can do this, and they are.

    But what about all those corporates with time and money invested in MS technology written for specific MS browsers. We don’t want them to break like they did with IE 7 do we. That’s a marketing no no for MS. Hence the corporates with non standards based code win.

    Standards 0, Corporate 1

    May as well pack up the standards and go home.. really we wanted to turn the corporates around, was going to be a slow long term job, but it was possible. But MS just caved and gave them a “Get out of Jail” free card.

  4. Russ says:

    @ Jermayn: correct. From what I understand, IE8 will simply freeze in IE7 mode. This means that if we want to have IE8, IE9 etc supported, we have to TURN THIS FUNCTION ON. Seeems insane to me.

    @David: a different scenario, but agree that it has flashbacks to a darker time!

    @Gary: An interesting way to look at it! :)

  5. [...] A furore has erupted over the past couple of days within a section of the web development community over a decision by Microsoft to require web developers to add a meta tag to their pages to define what version of Internet Explorer a site has been designed for. I’m not going to go into the pros and cons of this decision as it’s been comprehensively covered elsewhere. What I’d like to discuss is what this decision means for the average site owner and what they can expect when IE8 comes out (no firm date yet, but some time in the first half of this year). [...]

  6. [...] Marcy nos aporta esta magnífica recopilación de enlaces sobre el tema [...]

  7. [...] This might be a bit heavy for only being the second post on our newly created blog but since everyone else and their lemur have already weighed in on the subject, I thought I’d step up as well. [...]

  8. [...] matter Me, IE8 and Microsoft versioning Posted inWeb Standards | | You can leave a response, or trackback from your own site. This isbroken [...]

  9. [...] IE8 and versioning – very worrying developments by Russ Weakley (Links for more reading). [...]

  10. Hello all,

    Question: What will happen if we do NOT add the infamous line to our websites??

    My answer: your websites will render with IE 7 pseudo-”standards” rendering mode where we know that at the very least 750 bugs (spec. violations, incorrect implementations, faulty implementations) happen. Several parts of the DOM 1 & DOM 2 (roughly 500 methods, attributes) and CSS 2.1 will also be unsupported.

    Visit my webpage to see for yourself

    Regards, Gérard

  11. 3Easy says:

    eJohn posted a follow up to his MetaMadness article on the following day, which I believe is worth a peek: HTML5 Doctype

  12. Great articles……….I guess the brower wars continue