Since my conditional comments target less than or equal to IE7 or 6, then anything fed to IE8 is code for real web browsers, and yes, IE8 seems to be mostly acting like one.

I don’t get where I’ve read on the ie blog, advising on not using “edge” in production but using “IE8″ in the meta tag. Do they think it’s likely that their future browser development will stray from the standards path it is on, and they just might make IE9 horribly broken? We develop assuming all other web browser’s newest versions are “edge”. Should I not look forward to future versions of IE implementing even more standards rather than less?

BTW, when reading about ie8 rendering modes and version targeting, note the date of posts you find, as much reaction was generated the beginning of 2008, then ms reversed their decision for ie8 to operate in standards mode by default, much to the relief of the web development community.

Related, and more tame
IE6 Update

While I did successfully test a regular IE8 install, combined with tredosoft’s IE7 standalone, and Multiple IE for IE6, I ran across this surprisingly sparsely mentioned alternative, Internet Explorer Collection.

Again, with the regular installation of IE8, I used Internet Explorer Collection for IE7 + 6. It’s a tidy installer, including the developer toolbar that works in all versions (first time I have this working with IE6!)

Both these solutions have the issue of form selects not dropping down, instead triggering the popup blocker notification even when disabled, on 8 + 7, but works in 6, and text fields receive focus only in IE8.