As a remember: All of these work great in Webkit. Some of these things don't work right in Firefox (the drop shadows are rendered very badly, for example). And none of them at all work in any type of common IE.
And yes, very lame that IE gets none of these. None!
Chrome fails at a lot of Webkit standard stuff.
-webkit-border-radius: 3px 6px 8px 10px;
Currently, those have to be defined as separate attributes for each corner for this to work. Would this be considered a bug in WebKit? This is their proprietary attribute, so they aren't necessarily supposed to behave as the W3c specifies...As to the "bug in WebKit", only if it's supported in that version of webkit. Restart Chrome, and if it's still there, hunt for an existing bug report, and check if it's supposed to be supported. If yes, it's a bug. If no, then wait until a Chrome update (no clue how often they'll update the WebKit part of it, though).
I just don't think it would be too hard for Moz/Webkit team/IE team to agree to support 'border-radius' and other things. Any smaller browsers would catch on soon enough anyway.
Well, getting the IE team to get it to work may be a challenge.
If anything, the W3C exists to make sure the standards don't conflict with themselves. When amateur spec-designers start throwing around specifications, run for the hills. There's going to be enough hellfire, brimstone, and general fail to satisfy any armageddon cult, but they'll all disagree on how the fail is going to happen. Endless hours will be spent in chatrooms and forums debating which fail will win, and in the end everyone has to crawl into their radiation-, mutant-rat-, gelatinous-ooze-, cosmic-ray-, alien-proof-bunkers every 37 minutes just to survive the onslaught of potential fail.