Internet Explorer 8.0 to pass Acid 2 Test

With Beta 1 targeted for first half 2008, the folks at Microsoft are now saying that as of last week, IE8 reached a core milestone: IE8 in standards mode now correctly renders the “Acid2 Browser Test”. Acid2 is a test that determines how well a browser works with several different web standards. I posted about this earlier, mentioning that not even the current edition of Firefox handles the acid2 test correctly. Of course I was quickly reminded by commenters that it did a much better job than IE7, and that's true.

But the best news (besides the obvious fact that Microsoft embraces and sees the need for standards) is that they are going to do it in a way that doesn't "break" existing pages written for IE5 or IE6, or for the standards mode of other browser brands:
Modern browsers typically have two modes to render web pages, “quirks” and “standards.” MS says their experience with releasing IE7 taught them that many web sites today expect the browser to have IE6-compatible behavior. They say that with IE8 they have a "deep obligation" to interoperability and compatibility with existing web sites, and this has led them to add an additional mode to enable supporting industry standards even better.

So, developers can now write sites based on standards, insert a flag that tells IE to render in IE8 standards mode, and IE will then switch its rendering engine to use this new mode. This allows pre-existing sites to continue to work, and developers can opt-in to the new rendering engine on their own schedule. (Of course I should hasten to add that if all the players were with standards from the git-go, there wouldn't be a need for any of this BS).

For compatibility purposes IE8’s rendering engine defaults to “quirks” or “standards” mode. Site developers will need to insert a new opt-in flag to request the page to render using “IE8 standards mode.”

Overall, I'd say that this is pretty good news. I might even sign up for the beta. Now I just have one question:

When I visit a site that has embedded Flash or other video, is IE 8.0 still going to grey-screen on me and go straight down the potty, forcing me to use Firefox, or are you guys planning on fixing it?

Comments

  1. Anonymous1:16 PM

    Could you notify Mr. Opera of this so that he can finally get a night's sleep?! This is definitely good news.

    By the way, I have no problems playing embedded videos in IE, but I am still running XP.

    ReplyDelete
  2. peterbromberg2:58 PM

    Josh,
    XP vs Vista is a whole nother controversy. Not gonna go there...

    ReplyDelete
  3. Rick Strahl5:33 PM

    Peter, I think your talking about the the 'click to activate' thing in IE right? I think that's about to get fixed when Microsoft settled their suit with the company that claimed a patent on that. The fix is supposed to show up in the next round of IE updates.

    ReplyDelete
  4. peterbromberg6:44 PM

    No, not the Eolas fix - just that on some pages with embedded videos, IE craps out completely and you're sunk. There are probably a hundred fixes for this, all different, and most of them don't seem to work permanently. Firefox never seems to have a problem on these same pages.

    ReplyDelete

Post a Comment

Popular posts from this blog

Some observations on Script Callbacks, "AJAX", "ATLAS" "AHAB" and where it's all going.

I've taken a more than cursory interest in the whole Remote Scripting (.NET species) vs. AJAX and now ATLAS discussion, mostly because I started using Remote Scripting since Microsoft first released it, and because I continued to refine it after seeing Brent Ashley's excellent work with JSRS, which was one of the first "real" cross-browser solutions back in 2000 (that's the turn of the Century for you history buffs). Now Bertrand Leroy, a Microsoft guy whose work I like , has authored some very interesting ASP.NET 2.0 script callback stuff that he points to on his blog, and he is obviously (at least, to me he is) involved quite heavily in the development of this new ATLAS infrastructure that they'll preview at PDC. Leroy's most recent post brings to the surface what I agree are the major differences between the "AJAX a - la .NET" approach as popularized by Michael Swartz with his AJAX.NET library, and Leroy's RefreshPanel, the ASP.NET 2.0 b
Read more

IE7 - Vista: "Internet Explorer has stopped Working"

Image
This one was a bitch. All of a sudden for no reason at all, out of the blue, I get this dialog "internet Explorer has stopped working". I didn't install any new software, crap- I didn't do anything! So here I am using FIREFART to go on the internet and find out what to do! Damn! Good thing I've got the sucker on the same machine (I'm not "anti-Firefox", i just don't use it that much except to check my page renderings). The Fix The fix (at least for me): 1) Go into Control Panel, and choose "Internet Options". 2) Under the "Advanced" tab, press the "RESET" button at the lower right: Don't ask me why this happens, or why the fix works. That's a BUG, D00D - I don't care how you slice it!
Read more

FIREFOX / IE Word-Wrap, Word-Break, TABLES FIX

One of the most annoying things a developer (who would normally delight in writing code, not futzing with markup) can have is getting rendering issues between different browsers. The two biggest players are of course Internet Exploder and Firefart (as I lovingly like to refer to each). In most cases that's going to take care of 98 percent of your total site traffic. IE has had a proprietary "word-break" style attribute for a long time, and this made it into the CSS 3.0 spec. But that doesn't necessarily help you with Firefox right now. Firefox literally - (and I consider this completely idiotic, since it's been in their bug database for FIVE YEARS) does not have a reliable CSS style element to force table cell content to break in the middle of a word in order to stop the content from expanding your table / div off the page or over other content on the page. Here's a partial fix, which will work for most tables and browsers. The style declaration (I call it m
Read more