71 By this logic

then we have to do the following …

Sometimes it is just necessary to bite the bullet and move forward (analog TV, Betamax, 8-trax, tapes, HD-DVD). Microsoft backed the wronge horse (themselves) and lost, suck it up and move on. (add more cliche sayings here)

posted at 10:30 pm on February 29, 2008 by David Gutierrez

72 Microsoft makes a turn

After getting all these famous people here at ALA to agree (well, some at least), Microsoft now tells us (or so I understand) that they were wrong: http://blogs.msdn.com/ie/archive/2008/03/03/microsoft-s-interoperability-principles-and-ie8.aspx

I’m glad. But why did all the famous, well respected people not tell them straight away that this should be the way to go? Why did they, at least this time, no stick to asking for respecting standards?

posted at 12:51 pm on March 4, 2008 by Christian Marquardt

73 How is this different

I’m not understanding how this is different from the problem that overtook the old DOCTYPE solution… What if something like Dreamweaver or FrontPage or some other future web site development software decides to “help” the user by inserting this meta tag — doesn’t that mean we end up in exactly the same place in the end? That is, is it not still possible we may end up not being able to assume the meta tag actually means what it says it means?

posted at 10:58 pm on March 5, 2008 by Mecandes Almaradon

74 IS YOUR FACE RED?

Well is it, Jeffrey? And all the rest of you who felt that if it was ok with Jeffrey then it must be ok with you? Well it wasn’t OK. And others (especially those on a different continent – there are other continents you know) defended web standards against Microsoft. So, like spam in the EU, it looks as if you will have to opt in for IE7 compatibility. Next time, just say No.

posted at 11:49 pm on March 30, 2008 by David Leader

75 Untitled

If doctype switching is not a reliable method for indicating whether a developer has built their site to be standards compliant or not, then who says that version targeting will be any better. What is to stop uninformed developers from targeting standards based rendering but not actually using it in their code – thus breaking their sites just as uninformed developers who used the strict doctype but didn’t build their sites accordingly saw them break in IE7.

posted at 09:19 pm on April 2, 2008 by David Clark

76 Well ... there went that

Just to reiterate, from the IE blog (linked to above):

[blockquote]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. …
We think that acting in accordance with principles is important, and IE8’s default is a demonstration of the interoperability principles in action.
[/blockquote]

So that leaves us where we started. But, although I would not have minded nailing down pages to a version of IE (since we already often have to add IE if-statements), I dislike the idea of having to add special code for [em]any[/em] browser, search engine or anything else. That said, as browsers are released (and we’re talking years and years here), there will be display problems for older sites.

posted at 11:57 am on May 1, 2008 by Diane Vigil

77 Long-term feasibility of version targeting

To some extent, I agree with the article. However, I think that version targeting is, though a great solution on short-term basis, not feasible on the long-term.

1. First of all, let us examine the fact that there are lots of developers/designers out there who sort of fall in between the two groups of knowledgeable designers and ‘unenlightened’. I’ve been one for years myself.
   Imagine being an intermediately skilled web designer. You’ve heard of CSS and try to implement it in a standards-based way to the best of your knowledge, but your main goal is to make a cross-browser compatible website. How can you be expected to know of the “X-UA-compatible” switch and how to implement it? In fact, I only recently found out about the “almost standards” mode in browsers, and had believed all my pages to be running in strict mode for years, even though this wasn’t true for some of them. As an intermediate web designer, you can’t be expected to read ALA on a regular basis. The problem with the version targeting is that it doesn’t accommodate the users in between the ‘two groups’. This opt-in behaviour will give millions of people, professionals and hobbyists alike, severe headaches while they’re trying to figure out why even the newest Internet Explorer won’t look like Firefox and Opera. Or worse – why Firefox and Opera won’t look like the newest Internet Explorer.
2. Then, there is the long-term feasibility of this switch. I think it is unrealistic to have IE42 behave like IE7, because before long people – yes, even the unenlightened – will start to take notice of this behaviour (especially since IE is loosing market share by about 5 % a year, source ).
   Now, “Quirks Mode 2.0” might be just displaying pages differently, but if “Quirks Mode 2.0” really behaves like IE7, it could, in the future, also mean not supporting new features, which will start to become very noticeable at the time IE9 or IE10 is released.
   And how will we know that this is the last ‘switch’ Microsoft is ever going to come up with? I’m not quite convinced.
3. And now, about web standards. Though version targeting is presented as a feature advocating standards based design, I think this is not the right thinking of Microsoft. Surely the knowledgeable developers who already embrace web standards will continue embracing web standards, but implementing this switch will never bring web standards to the masses. In fact, it will throw up yet another barrier, and probably not the last.
4. Ironically, the web sites that will actually “break” to a catastrophic extent – e.g. illegible or unusable – are probably the web sites authored by the knowledgeable designers anyway, who know of the X-UA-compatible switch and how to implement it. It kind of beats the purpose, doesn’t it?

1. Now, please consider this: “Breaking the web” will never, ever, be a more shocking user experience than the transition to Firefox, iCab, Safari, Opera, the Wii Browser, the iPhone browser, etc. A transition which is usually not really that noticeable at all – at least in my experience. The only web site that won’t work in my beloved Firefox is the **** Microsoft Update… Just to make a point.
   Now, one might argue that “…zillions of people who don’t know any better do tailor sites to the quirks of IE6,” and that “That’s why an improved IE7 “brokeâ€? old sites.”
   From this I gather that websites are “breaking” more severely in IE7 than in Firefox or Safari because web designers are using workarounds such as CSS filters, the holly hack, and conditional comments (in fact a form of version targeting itself) to code for the quirks of IE6. Maybe I’ve misunderstood, but I think the correct solution to this problem would be making IE8 so that it would behave exactly as other standards compliant browsers – removing support for the Holly Hack, conditional comments, etc.

Freezing the web might just not be the smartest thing to do. Especially since Microsoft hardly makes the rules anymore. I would be interested to hear what the W3 Consortium has to say about the matter. Maybe they can offer a better solution.

posted at 05:20 pm on August 16, 2008 by Lennart Goosens

78 IE8 Grrrrrr

I have downloaded the Beta of IE8 and I am not really that impressed. It breaks an amazing scrolling javascript function on my company’s homepage. Does this mean a new set of hacks for IE8? I did like the reference “We might call them the unenlightened” in the article.

posted at 07:50 am on September 25, 2008 by beau vignes

79 let em break the web, it was never theirs in the f

We are microsoft. We are the standards. Resistance is futile. You will be assimilated.
Every time I read an article about Internet Explorer those words go through my head.
It’s basically all promises and only 20% of those promises get delivered.
I think microsoft is still in brand loyalty mode and that will never change.
Who created all these hack web-masters in the first place? Netscape was bundled with windows not that many years ago only 15.
They do know they can brand firefox right?
The only way to have standards compliant web developers is to have a standards compliant web browser, even if joe newguy is just starting to learn building webpages if something breaks they will learn standards.
For those who call themselves developers and don’t follow the standards then hey let their websites break, it their own fault anyway. Maybe they will thank Microsoft for helping them code better.
It’s best for their bottom line to follow these standards.
If they don’t you can always add this line to your website
“Best viewed on a good Web Browser” with links to opera, firefox, etc..

posted at 06:58 pm on February 3, 2009 by david Siembab