Linked by Thom Holwerda on Wed 19th Dec 2007 21:48 UTC, submitted by RJop
Internet Explorer "As a team, we've spent the last year heads down working hard on IE8. Last week, we achieved an important milestone that should interest web developers. Internet Explorer 8 now renders the 'Acid2 Face' correctly in IE8 standards mode." Insert freezing and hell joke.
Thread beginning with comment 292244
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Great!
by WarpKat on Wed 19th Dec 2007 22:17 UTC in reply to "Great!"
Member since:

IE8 now renders the “Acid2 Face” correctly in IE8 standards mode.

What does it mean "in IE8 standards mode?"

One person brought up an interesting point on the blog (near the bottom as of this writing) - if IE8 has two modes, then it's useless.

Reply Parent Score: 14

RE[2]: Great!
by sappyvcv on Wed 19th Dec 2007 22:19 in reply to "RE: Great!"
sappyvcv Member since:

I assume [hope] it's a default mode for all sites to render correctly. Then for any site which relies on old broken IE behavior, THOSE specific sites are rendered in "compatibility" mode.

Reply Parent Score: 6

RE[3]: Great!
by Beta on Wed 19th Dec 2007 22:37 in reply to "RE[2]: Great!"
Beta Member since:

It’ll be enabled when the right conditions occur, much as “standards compliance mode” is activated now.

Google will tell you a lot more, but it’s normally a case of selecting a strict doctype for the document, assuming the document is conforming.

Reply Parent Score: 4

RE[3]: Great!
by danB on Wed 19th Dec 2007 22:54 in reply to "RE[2]: Great!"
danB Member since:

Actually, my guess is that "standards mode" simply refers to the "usual" mode for rendering web sites which have a correct DOCTYPE declaration etc... (as opposed to the so-called 'quirks' mode, see )

This strategy of having two modes is pretty common, not just with IE but also with other browsers.


Reply Parent Score: 3

RE[3]: Great!
by BrianH on Wed 19th Dec 2007 22:55 in reply to "RE: Great!"
BrianH Member since:

Ever since version 6, IE has had a "standards-compliant" mode and a "compatibiltiy" mode equivalent to Firefox quirks mode. The quirks mode is basically laid out like IE4, and the standards-compliant mode is supposedly laid out according to web standards, though the actual compliance with those standards has been improving gradually. IE7's standards-compliant mode is actually pretty good - though not all the way there yet, IE7 can render most pages pretty close to the way they would render in Firefox and such.

You have to trigger standards compliant mode by including a proper doctype declaration. There are pages on MSDN that list the doctypes that will trigger it, a pretty long list that includes all modern HTML 4 or XHTML 1 standards.

MSDN changes their linking structure pretty often, but this page seems to work right now:

Edit: Got the initial version wrong (is IE6, not 5).

Edited 2007-12-19 22:57

Reply Parent Score: 3

RE[4]: Great!
by angryrobot on Wed 19th Dec 2007 23:01 in reply to "RE: Great!"
angryrobot Member since:

Both IE AND Firefox have a quirks mode and a standards mode. If you use the correct DOCTYPE and have valid code, they are supposed to render the page according to W3C standards, otherwise they revert to a compatibility mode for older, non valid HTML. There's lots of good reasons for this.

Reply Parent Score: 4

RE[2]: Great!
by KugelKurt on Wed 19th Dec 2007 23:38 in reply to "RE: Great!"
KugelKurt Member since:

Every browser engine I know has at least two modes:
Standards compliance mode.
Quirks mode.

If a HTML file has a correct header, the browser usually tries to render the HTML file according the specifications in the header (like HTML 4.0 strict etc.). If the renderer detects lots of errors, it falls back into quirks mode. The quirks mode is the really hard part to program in a renderer. It tries to interpret common mistakes by web page authors the way they might have intended it and not how a standard decribes it. The quirks mode is the mode older KHTML versions and iCab lack. That's also the mode Apple vastly improved in WebKit compared to older KHTML releases.

At least Firefox shows you which mode it's using: Use Tools -> Page Info ("General" tab).

Reply Parent Score: 3

RE[2]: Great!
by flump on Wed 19th Dec 2007 23:39 in reply to "RE: Great!"
flump Member since:

I thought that would be similar to Firefox's "Quirks Mode". I could be wrong on this, but I thought Firefox had a Standards and Quirks Mode.

Quirks Mode would be applied on sites that do not apply the proper doc type. At least that was my understanding.

Reply Parent Score: 2

RE[2]: Great!
by nberardi on Thu 20th Dec 2007 00:59 in reply to "RE: Great!"
nberardi Member since:

With HTML there are a couple of doctypes at the top of the page. There is strict which is usually considered standard mode. Then their is traditional or loose which allows backwards compatibility. This is all dependent on the web developer not personal settings of the browser

Reply Parent Score: 1

RE[2]: Great!
by andrewg on Thu 20th Dec 2007 08:43 in reply to "RE: Great!"
andrewg Member since:

Firefox and Opera must be useless then. If you are browsing OSNews in Forefox right click on an empty part of the page, select 'View Page Info'. Look for render mode. You will see it says 'Quirks Mode'. I believe all browsers do this. I like developing in XHTML 1.0 Strict as browsers seem to have the least differences that way. All browsers need to have different modes. If the detect missing, bad or old documents types then they default to the 'quirks' mode. If it is well formed and modern they use the standards compliance mode.

Reply Parent Score: 2

RE[3]: Great!
by KenJackson on Sat 22nd Dec 2007 06:43 in reply to "RE[2]: Great!"
KenJackson Member since:
2005-07-18 'View Page Info'. Look for render mode. You will see it says 'Quirks Mode'.

Now press CTRL-U or click View -> Page Source.
You'll see that OSNews does not supply a DOCTYPE tag. That's why Firefox displays it in quirks mode.

Reply Parent Score: 2