I think this is it:
http://aneventapart.com/alasurvey2008/

[The link is working again---it's supposed to point to the article announcing the results. -E.]

I’m having difficulty figuring out what the width percentages are accomplishing.

Thanks again for your great CSS work!

well, you are to be congratulated heartily
for eating your own dogfood, as well as
for being honest about how bad it tastes.

hopefully it shows how far you have to go,
especially since you needed to reach ahead
to html5 just to accomplish what you wanted.

i, for one, won’t pay much attention to you
standardistas until you can convince even
the unsophisticated among us how _easy_
it is to create ordinary stuff like these charts,
not how _hard_ it is, or what kinds of hoops
we need to jump through for all the browsers.

which, i would hazard a guess, means that i
won’t be paying any attention any time soon.

but surely you must be glad that you no longer
have to eat that .pdf, along with your integrity.

no matter how much work that might have took,
i’d guess that that alone was well worth it to you.

i repeat, congratulations on a job well done…

-bowerbird

Right enough, Bruce– though I feel compelled to mention that while Firefox users can upgrade their way out of the parsing problem, Camino users can’t unless they’re willing to run beta software. The auto-upgrade notices in Camino still push 1.6.7, which is based on the FF2 engine.

Anyway, I’m going to revisit some of that stuff in the near future, as I prepare to also revisit the AEA markup.

Josh, as I said, we almost did that (or at least something very much like it). I was a little wary of taking that approach with Google Charts, though, since it meant the charts would fail if the GC service were unavailable. And I didn’t want to pull the images off GC and embed them for accessibility reasons. Had we decided to go the JS route, I’d probably have used something like Bluff with a JS script as a go-between to scan the tables and construct the Bluff calls. But why do that when I could pound my head against the CSS and see if I could pull off the seemingly impossible?

Joe, do you mean you don’t know of a device that bothers to use tfoot to create a running table footer (as thead should create a running table header) in paged media?

I understand the how and why your reset.css does what it does, but why can’t you add :focus to wherever you add :hover just in case there might be someone who uses a keyboard in a browser that’d recognise the dynamic pseudo class selector to figure out where they are in the documents?

Lately, my approach has instead been to use a bit of JavaScript to convert plain tables into Google Charts. Doing that, it turns out that bar charts, pie charts, and line charts are pretty easy to wrangle. I blogged about it with an example here: Turn Your Tables into Spiffy Charts