I don't think it's a good idea (I think it's opposite of that) to use not yet closed parts of css3 specification in production. I mean, it's ok as long as it works without it. This code is full of vendor specific prefixes. They only add in size and many of them doesn't have reliable fallback.<p>Also, these buttons look close to horrible (as in unreadable) in browsers that doesn't support all features used. I only tried quite capable Konqueror but I'm affraid what would they look like in IE7. Another thing is that this is 16kB (uncompressed). 16kB for social sharing buttons that doesn't really stand out that much (as opposed to css(2)-styled buttons) and add no extra functionality to the user.<p>So, please, think twice before using them.
These are nice, but you should also check these out as well <a href="https://github.com/adamstac/zocial" rel="nofollow">https://github.com/adamstac/zocial</a> ... homepage here: <a href="http://zocialbuttons.com/" rel="nofollow">http://zocialbuttons.com/</a> ... there are MANY <a href="https://github.com/adamstac/zocial/blob/master/stylesheets/partials/_mixins.sass" rel="nofollow">https://github.com/adamstac/zocial/blob/master/stylesheets/p...</a>
For Facebook, Twitter, GitHub, Google, Yahoo!, Windows Live ID, OpenID.<p>Includes icons and two sizes of button.<p>This code formed the basis of the sign-in buttons I used on this UK deal-sharing website: <a href="http://www.oodeals.co.uk/login" rel="nofollow">http://www.oodeals.co.uk/login</a>