The ever confusing world of IE8's compat modes.

"Approximate IE6/IE7 quirks detection logic"

Hard to believe the "Close Your Tags" section is entirely accurate... that one would observe a noticeable speed difference in rendering... seems ideal for a benchmark test

Trident's Key event flow-chart

"We strive to make Compatibility View behave as much like IE7 as possible, but we do make exceptions. Many of these exceptions enable improved security and accessibility features immediately, even for sites that have not yet migrated to IE8 Standards Mode". Well this is helpful, there's some changes from IE7->Compat Mode on here I hadn't noticed yet.

Hrm, seems that sites in the compat mode list can be found in: "res://iecompat.dll/iecompatdata.xml

The IE logo licensed under creative commons, I need me some IE logo remixing.

"In this case, the ampersand ends up in the string as a plain ampersand. But when the time comes to set the document location, IE applies another entity replacement, while other browsers don't. In IE 6, this code results in a visit to a URL with a copyright symbol in it."

"This document is meant to provide web application developers, browser engineers, and information security researchers with a one-stop reference to key security properties of contemporary web browsers. Insufficient understanding of these often poorly-documented characteristics is a major contributing factor to the prevalence of several classes of security vulnerabilities."

"Marginalia is an open source Javascript web annotation system that allows users of web applications to highlight text and write margin notes."

Well, I'd say that's more of a JavaScript mystery than anything else. Apparently implementations agree, because only Firefox does something different than the other major engines.

An older article but worth noting for internet history/anthropological study of certain best practices.

list of MS CSS properties, type, and their W3C status

"The interface objects (constructors) and interface prototype objects defined for Beta2 are based on the structure and function of IE's internal object model. Early on, we had to decide if we wanted to implement a "fake" layer for the constructor/prototype objects that looked identical to the W3C model, or to expose what we had, warts and all. While the warts weren't particularly attractive, they do help to bring clarity to the way that the DOM is represented internally and avoid having a whole series of internal mapping bugs between what is actual and what is veneer."

"Sending the new X-Content-Type-Options response header with the value nosniff will prevent Internet Explorer from MIME-sniffing a response away from the declared content-type."

Not really sure wha the animated GIF is supposed to show... other than the fact that the vertical spacing on the W3C site looks like crap in compability mode.

Apparently IE's performance of string concatenation using the + operator (instead of array or stringbuilder methods) sucks. Also seems to be fixed in IE 8. Yay?

A *much* better <canvas> plugin for Internet Explorer - based on Firefox's <canvas> implementation

Looks the "IE7" patch library moved to Google Code at somepoint.

Seems to focus on customization and cornering the 3rd-party desktop browser market in Japan. Uses Trident (what version though?) as the rendering engine. One of the plug-ins looks like it offers Firebug/Web Inspector features.

huh.

Or why IE's handling of <object> is a pain in the ass.

Images and PSD files representing common HTML form elements organized by operating system & browser.

or "you think the DOM is a crazy mess now, just wait."

thoughtful analysis of "almost standards mode" and IE 8's versioning switch

Why DOM work can be really painful

crappy page title - it deals with IE's nasty bug concerning z-index positioning and select form widgets.