CSS3Generator.com has been online for at least few months, mentioned everywhere tons of times. Its examples have been used to create tens (if not hundreds or even thousands) of CSS3 showcases and cheat sheets.

Here is an example that grabbed my attention:

box-sizing: border-box;
-moz-box-sizing: border-box;
-webkit-box-sizing: border-box;
-ms-box-sizing: border-box;
-o-box-sizing: border-box;
-icab-box-sizing: border-box;
-khtml-box-sizing: border-box;

As far as I am concerned, Firefox and the browsers based on WebKit (Safari, Chrome and the latest version of iCab) require prefixes, indeed. However, Internet Explorer handles box-sizing just fine since version 8. Same with Opera since version 7 (not 9.6 as the generator suggests) and Konqueror since version 3.4. Also, regarding browser compatibility, according to Mozilla Developer Center, Firefox handles box-sizing since version 1 (not 3) and Safari since version 3 (build 522, not 3.1+). Chrome, presumably, has it since version 0.2 (as it was built on WebKit 522). That is a lot of inconsistency and bloated code on a website that has been linked by pretty much anyone in the industry.

That leaves us with a much shorter version of the universal (read as: much more universal as the generator suggests) box-sizing implementation:

-moz-box-sizing: border-box;
-webkit-box-sizing: border-box;
box-sizing: border-box;

Note the vendor-specific prefixes before the main, non-specific property.

Please do not get me wrong: we all make mistakes and we all suffer from time shortage these days but please think about the consequences of linking sources that has not been entirely checked. We talk about what HTML5 is and what it is not, yet we miseducate others at the same time (as this example shows, let alone the extra bandwidth caused by the bloated code).

During the pursuit of the pure, semantically correct web with all the great things that HTML5 and CSS3 provide these days it is hard to not notice the fact that we lose our grip a little bit and we should really *think* about the hype we are all in.

Dude i think it’s better to say whow, than you guys just spit this thing over, for you guys yes, maybe you guys are the expert one, but think about others to learn about this… it’s better if you guys help him but not to comment a things that no one would like, dont just critic but use it wise to teach others..

Even though IE8 got problems with this tools yet is too good to learn .. :)

Andrew Roberts: you got some skill why dont you try chris and tell him about it, dont make it annoying with some inviting to ur site, learn then teach, not teach then learn.. :)

I’ve learnt a lot in here, so guys if you come and just want to critics the #css that has been shared with you guys, it is better to tell the microsoft about their software to learn more about CSS3..

Be fair with others..
I learn so much from this website, dont make it hard to others..