Randy, great one. Yeah I think we were all feeling the need for a tool.

Blepore, good catch. The post says it’s should be fixed by IE8 final, so the issue should be moot, but I’ll switch them anyway. :)

The @font-face declaration is a bit of a hack, but it certainly doesn’t necessitate two rules. On my bulletproof @font-face syntax post I detail how exactly we got there and whats up with compatibility.

Yes, that’s a cool idea about showing the new CSS3 stuff. Even if I like this stuff coming into the browsers and I appreciate that browser programmers are working on that stuff, this examples shows the mess and some failings of nowadays inter-browser-vendor-communication. CSS3 provides so many new things and all browser vendors start working on that snippets across everywhere, they all work on different constructions. Instead of focussing one, agree with one naming-convention, fixing leaks within the specs, they all show up with different solutions. Hooray :(. Whereas box-shadow and border-radius (IE lacks here) looking pretty consistent and the -browser prefixes could be reduced, others like gradient look different each engine. At what cost? Even browser programmers need to look twice in their code until they could wait for the -browser prefix to be reused. At what cost?

@randy: nice, but I am missing seeing changes on-the-fly. Also, the fonts are a bit too much :)
@PaulIrish: it would be more usable for my use case if it used a more “traditional” color scheme (black background is exactly the opposite of what I use in 90% of our webites)