In the middle of moving all those underscore delineated URLs to dash delineated URLs*, Google went ahead and announced the rel="canonical" scheme for defining the preferred URL for a piece of content. While it's not the biggest deal for me, other than the "/" vs "/index.php" question, for many people with more dynamic systems it's a big deal. Bravo to everyone involved as it's a really straightforward, easy-to-implement solution to a common, troublesome problem.
(more…)

Right now Internet Explorer 6 averages about 10-12% of my traffic here (11% for the past month.) While I won't dismantle existing support mechanisms, I will no longer test new features in IE6 and going forward I will not support or test for IE6 for the new version of the site.

The good news is, I rarely do anything here that will tax IE6 heavily and the redesign will likely be architected in such a way that it will probably work pretty well in IE6 even without specific attention. The bad news is, 11% equals about 6000 people and the thought of annoying, even slightly, that many folks over a month worries me. The thing is, I just can't support three versions of a browser, especially when one of them is such an odd man out. IE7/IE8 are comfortably supportable browsers. IE6 plainly sucks.

Spurred on by this:

Microsoft: IE 8 won't be done until 2009

So I've got to draw a line in the sand.

Now if I can just convince them to do the same at work…

Lost in the past few years of IE6 based stagnation (and ensuing developer angst) is the fact that the Internet Explorer team have come up with some pretty cool enhancements to the way we build web sites over the past ten plus years.

So, while we're cheering on Firefox's growing market share, hesitantly eying IE8 and waiting for the ugly stepchild of the browser landscape, IE6, to finally die a painful (and hopefully immediate) death, I thought I'd lay out some of the innovations introduced by Internet Explorer to remind us of relatively positive days gone by*.

As a fun exercise, while you're reading this, compare these innovations to the black hole left in the web development world by the long and terrible reign of IE6. It's an interesting juxtaposition of help vs. harm. Here's hoping future versions of the browser continue to trend closer to the "help" line as IE7 has and IE8 appears to be doing**
(more…)

To make use of the native getElementsByClassName I rewrote my getElementsByClass function to use the method where possible.

Here's the code*:
(more…)

With the recent release of Firefox 3, we've now got a full fledged, mainstream browser that supports the long-awaited, often replicated, getElementsByClassName method. This is good news as we'll all be just that much speedier as we ditch the various helper functions and go right into the browser for that functionality.

The thing is, the transition, when we'll finally be able to make it, isn't a one to one swap. In fact, depending on what you're using it for you could run into problems transitioning from a helper function to the native method.
(more…)