This was originally a presentation aid and as such I only fully tested it in Chrome on a projector at 1280x960. I would like to keep improving the FF support in my spare time, and PRs are also welcome ;)

If you'd like to see the slinky in isolation, I've got a page up that has better compatibility: http://css3playground.com/slinky/

same here nothing shows on firefox but that is a small issue

the demo is extremely well done!

lucky you. i got a huge computer hang on my Iceweasel (firefox 17) with a beefy CPU but crapy 3d accel.

Performance was fine in chromium.

Works fine on FF except the slinky, and all of it works on Chrome for me. OSX

actually...

IE7: 0.5% worldwide

IE8: 8.65% worldwide

IE9: 5.29% worldwide

http://gs.statcounter.com/#browser_version_partially_combine...

The real question is whether you want to invest the time needed to create a fallback for those users. Websites that use the new CSS things as a primary thing (like this presentation) won't work, but sites where the newfangled CSS things are used just as embellishment - dropdowns, sliding menus, spinners, you name it - will remain functional, just not as pretty.

tl;dr graceful degradation / enhancement.

It says css 3d, which those browsers doesn't support.

OT, but if you upvote an article, it gets saved into your "saved stories". You can find the link on your profile if you click your username in the URH corner.

Your "saved stories" URL would be https://news.ycombinator.com/saved?id=Kiro