Microsoft has jumped on the ditch-IE6 bandwagon with IE6Countdown.com, following in the footsteps of such campaigns as Browse Happy, End 6, and Save the Developers.

Of course, since it’s a Microsoft-sponsored campaign, it’s only promoting upgrades, rather than promoting an upgrade-or-switch message.

Static HTML points out why you might want to put your effort into some other campaign instead. Because IE6 Countdown is only an upgrade campaign, and IE6 users are all on Windows XP or below (Vista ships with IE7), they can only ever upgrade as far as IE8. Given the huge gap between IE8 and IE9 in terms of standards support, HTML5, CSS3, and so forth, IE8 will soon become the new millstone around the web’s neck.

So instead of plugging IE, consider plugging your own favorite browser, be it Firefox, Chrome or Opera. Or perhaps plug another switch campaign. After all, there are quite a few alternative web browsers out there!

The IEBlog recently posted about their efforts to improve reliability in Internet Explorer 8, particularly the idea of “loosely-coupled IE” (or LCIE). The short explanation is that each tab runs in its own process, so if a web page causes the browser to crash, only that tab crashes — not the whole thing. (It is a bit more complicated, but that’s the principle.) Combine that with session recovery (load with the same set of web pages, if possible with the form data you hadn’t quite finished typing in), and you massively reduce the pain of browser crashes.

I’d like to see something like this picked up by Firefox and Opera as well. They both have crash recovery already, but it still means restoring the entire session. If you have 20 tabs open, it’s great that you don’t have to hunt them down again. But it also means you have to wait for 20 pages to load simultaneously. It would be much nicer to only have to wait for one (or, if I read the IE8 article correctly, three).

Edited to add:

On a related note, I’ve run into an interesting conflict between crash recovery and WordPress’ auto-save feature. If you start a new post, WordPress will automatically save it as a draft. If the browser crashes, it will bring up the new-post page, but restore most of the form data you filled in. So the title, the text of your post, etc will all be there. But WordPress will see it as a new post, and you’ll end up with a duplicate.

This wasn’t a major problem when I encountered it — I had to reset the categories, tags, and post slug after I hit publish (since I hadn’t noticed that they’d been reset to defaults), and I just deleted the older, partial version of the post — but I can imagine if I’d uploaded an image gallery, I would have been rather annoyed, since there’s no way (that I’ve noticed) to move images from one post to another. Reuse them, sure, but not such that the gallery feature would work.

Acid2 reference image.After looking at how Safari 3.1 handles the Acid2 test, and finding that under some circumstances/platforms it fails the test, I realized: that one line, with the eyes, has been the cause of most regressions in browsers that previously passed the test.

Rows 4-5 test fallback behavior for objects. The idea is that if a page tries to load an external resource, but can’t—the file is missing, the server’s down, the network’s slow, the browser doesn’t have the right plugin, etc.—the page can provide alternate content. And it can be nested, so you can try, say, a video clip that falls back to an SVG image that falls back to a PNG that falls back to text. Continue reading

Internet ExplorerInstalled the first Internet Explorer 8 beta. Some thoughts:

I’m impressed that it can import settings from Firefox & Safari.

It detected Firefox extensions and even offered to look up similar add-ons. Unfortunately it was a big long search string with all the titles, and therefore a useless list of results for things like cameras (yeah, how am I supposed to install a $1000 Nikon D80 on my web browser?) and the hint book for Splinter Cell.

Activities: My first thought was, “hey, they’re doing stuff with microformats!” Which is key to the underlying support (recognizing types of data and only offering relevant services, like maps for locations but not for book titles). But on the face of it, it’s a lot more like the way Flock integrates with various web services: Set up your blogging provider, and you can easily send stuff to your blog. Though right now they mostly have Microsoft-hosted services.

“Emulate IE7” appears to involve restarting in an alternate mode right now. I assume automatic switching is something planned for later betas.

Other than that, the UI seems about the same as IE7 so far.

It does indeed pass Acid2 (assuming the page isn’t swamped when you try to load it).

So, how else does its rendering differ?

Minor visual glitch: I have CSS-based banners on some pages (W3C validation, for instance), using spans with borders. If it’s on the last line of a page, IE will cut off the bottom border, because it extends past the end of the page. Other browsers show it. I’ve gotten around this in the past by adding a blank paragraph afterward, but now IE8 collapses the empty paragraph. That’s probably the correct thing to do, but it does mean adjusting things a bit. Not a big problem, though, because I’ve just noticed that it handles other pages fine, without the <p></p> workaround, which means that I’m probably already using a better solution elsewhere.

Several cases of re-styling UL lists seem to confuse it. The tabs running across the top of my Flash page, for instance, or the sidebar on the Alternative Browser Alliance. Others appear just as they do in other browsers (including IE7). This will bear investigation. (Edit: 2 different problems; see below.)

Still no sign of generated content. Beta 2? Please? Edit: according to CSS3.info, it does support generated content, but images don’t work (yet?). I’d been using this, progressive-enhancement–style, to add icons for outgoing links on my Flash site. It works in, well, everything else current.

Additionally: I’m surprised to see it so early, and to see it as a public beta and not something that required an MSDN login. And they had the sense to release a version for Windows XP! I was half-expecting it to be a Vista-only release, which would’ve been seriously annoying.

Further updates will be added below as I think of them.

It turns out the problem on the Alternative Browser Alliance menu wasn’t related to lists as I’d thought, but to a change in the CSS parser. For whatever reason, IE8b1 is susceptible to the Caio Hack (/*/*/ place code here /* comment */) normally used to hide CSS rules from Netscape 4. At this stage I should probably be able to remove it and not worry about NS4 anymore. (And it turns out that since I added media types to the link a while back, NS4 doesn’t even read the stylesheet in the first place!)

On the issue with the tabs on the Flash site, it looks like IE8b1 isn’t extending backgrounds beyond the text line on inline elements (oddly, also like NS4). This is probably what’s really going on with the CSS buttons I mentioned above. I’ll have to check which behavior is correct, but my money would be on the Gecko, Opera and WebKit interpretation. If so, this will probably be changed before the final release. If not, I’ll use inline-block instead. Which perhaps I should be doing anyway, except for the annoying fact that Firefox 2 doesn’t support inline-block and Firefox 3, which does, is still in beta.

I’ve reported the Caio Hack issue to Microsoft using their “Report a Webpage Problem” tool. The form emphasizes that you shouldn’t send anything that could identify you, so instead of reporting the problem on one of my own sites, I sent the page describing the hack. This probably means I reported it in the wrong way. 😕

It looks like Activities isn’t actually context-sensitive yet, since it’s offering to show me a map even when I’ve selected random prose instead of an address.

Having messed with it more than I probably should over the last 24 hours, I’ve come to a decision: During beta 1, any rendering problem I encounter in IE8b1 that works the way I want it to in Gecko, Opera, Safari and IE7, I’m going to assume is a bug in beta 1. I’ll try to narrow them down & report them when I have a chance, but I won’t actually change my sites’ code (except for retargeting IE-specific workarounds) until at least beta 2.

Internet Explorer.I know global statistics still show IE7 only taking up 25%–35% of overall Internet Explorer usage, but stats on this site show a slightly different story (usually skewed toward the crowd more likely to install/upgrade a browser). For the first three days of December, I’m seeing more IE7 users than IE6.

Not by a lot. IE7 has 32.7% and IE6 has 30.3% of the total. And I expect it’ll level out or even reverse as stats from a regular work week filter in. But still, something has finally surpassed that moldering, zombified, shambling heap of a web browser.

Next step: getting Firefox’s numbers (currently 26.8%, also above the global levels) over IE6.

Come on, let’s put a stake in this relic. It’s done.

Update (Thursday): And now Microsoft is finally starting to talk about IE8…even if it is just to say they’ve picked out a name. Whee. 😐

As for the stats, the gap has closed somewhat in the last 2 days, with IE7 at 31.6% and IE6 at 31.2%. This is definitely looking like a home/office split. I’m going to have to write a script sometime to do a daily breakdown of browser versions and see if this actually fits.

Update (Saturday): Yes, IE6 has caught up. 32.2% to 31.1%. *sigh* It turns out I was just seeing a local maximum. 🙁