Presto, the new rendering engine from Opera, has created a quirks mode to 'emulate' buggy rendering of pages common among older browsing software. This is triggered by the DocType of the HTML page.
The final version of Opera has followed an IE-bug in that if you have anything other than <DOCTYPE...> on the first line of your page (e.g. you have a standards-compliant <xml...> declaration) then the browser uses quirks mode. This will change in future releases. This has been fixed in Opera V7.1
| Label | Definition | with URL | without URL |
|---|---|---|---|
| Label | Definition | with URL | without URL |
| No !DOCTYPE | Off | Off | |
| HTML (No Version) | Off | Off | |
| HTML 2.0 | Off | Off | |
| HTML 3.0 | Off | Off | |
| HTML 3.2 | Off | Off | |
| HTML 4.0 | No Definition | On | On |
| HTML 4.0 | Frameset | On | Off |
| HTML 4.0 | Transitional | On | Off |
| HTML 4.0 | Strict | On | On |
| XHTML | All | On | On |
| XML | On | On | |
| Unrecognized !DOCTYPE | On | On | |
To test whether Opera is in quirks or standard rendering mode, type the following into the address bar (or make it a bookmark):
javascript:alert(document.compatMode);
You should get an alertbox with the string "BackCompat" or "QuirksMode" if OperaQuirksMode is in effect, and "CSS1Compat" if Standards mode is in effect.
Note that the DOCTYPE switch only applies to HTML: XHTML pages served with the MimeTypes? "application/xhtml+xml", "application/xml", or "text/xml" will always be rendered in Standards mode, even if no DOCTYPE is used. There is an unofficial MimeType "text/xhtml" -- If a page is served with this MimeType, it must have a valid DOCTYPE for it to be rendered in Standards mode.
There *is* a DOCTYPE switch override in Opera 7.0, note however it is currently buggy (e.g. trying a standards override with NO DocType will still yield Quirks mode etc.)
Put this in your Opera6.ini under [User Prefs]:
CompatMode Override
If set to either 1 or 2 the switching mechanism is overridden as follows:
CategoryOpera
CategoryTechnical
Removed as it didn't apply to V7.2 anyway...
NonTroppo (2003-10-24 15:10:59)
Gah, broke the page by accident. Revert please?
pcd655220.netvigator.com (2004-04-15 05:45:32)
Bump comment to highlight the fact this page is broken under the Moosified wiki.
BtEO (2005-03-07 01:49:06)
Ian, the csswiki link *should* be recognized as external, whilst atm it is not.
MooseCSS (2005-03-30 01:41:18)
The CSSWiki link is working fine for me - an InterWiki link that automagically expands to http://css-discuss.incutio.com/?page=QuirksRenderingMode
NonTroppo (2005-03-30 14:55:28)
I do not see an extrenal icon for it. Do you? The link is working, but not the icon.
MooseCSS (2005-03-30 15:42:10)
Ah, understood. InterWiki links are deemed as transparent links, and are classicaly treated as "magic" internal links, just as a WikiWord is automatically expanded, so are Interwiki links. The "idea" is to allow wiki information to seamlessly mesh together, which is I assume why they don't get the external icon. Of course they are really external links, and so we can change this behaviour; maybe another icon for InterWiki links?
NonTroppo (2005-03-30 16:32:38)
No, it's okay — I am a creature of habit, and was just fooled by the lack of icon, thinking peripherally that it's a local wikilink. Browsing as fast as I do, I rely on consistency of traffic signals, you see. Red is red, and green is green! :p
MooseCSS (2005-03-30 16:45:01)
How to force browser to operate in Quirks Mode using javascript ?
85.89.168.120 (2006-10-12 05:57:47)
http://users.rraz.net/mc_on_the_rocks/testpage/temp/Op7test.html
This address, from first item of "Behaviours that should change in Quirks mode", does not exist (404 not found).
200.141.72.2 (2003-10-24 02:55:10)