Linked by Thom Holwerda on Wed 19th Dec 2007 21:48 UTC, submitted by RJop
Thread beginning with comment 292278
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-07-06
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).