If you’re like me, you love change, but not for the sake of it.
You look forward to the next iPhone, Android, console or OS release, not even knowing what’s in it, and feel disappointed every time, always wondering wonder why you were excited in the first place.
As a designer, the introduction of CSS3 was exciting, but like always, I felt inevitably, I would be let down. I didn’t know why, because I was too busy doing my tax return, or planning my next corporate takeover (and subsequent world domination) to read up on it extensively prior to release.
Having worked with it for a couple of years however, it’s plain to see this is one of the biggest changes to web development since people started caring what a website looked like.
The biggest difference between CSS2 & CSS3 is that CSS3 has been split up into a number of different sections called modules. Presently these modules are making their way through the W3C’s recommendation process.
CSS2 was originally submitted as a single document, with the Cascading Style Sheets information completely self-contained. AS a result of the modular nature of the CSS3 specification, we now see a far wider range of browser support for the new standard. Of course, any new specification requires testing, however it’s plain to see that with CSS3, you’re pretty safe across all the major browsers.