456 Berea Street
25th May 2007, 10:02 pm
As most designers and developers who use CSS on a daily basis know, it's been a while since a new CSS Recommendation was released. There are several possible reasons for it taking so long, something Andy Budd brings up in CSS2.2 (http://www.andybudd.com/archives/2007/05/css22/).
While I agree that the W3C's process is way too slow, I don't think we can lay all the blame on the W3C. Browser vendors are a big part of the problem. Especially one of them (you-know-who).
Of course there are many neat features in CSS 3 that I would love to be able to use now, but just imagine for a moment that all browsers had full support for CSS 2.1. They really should, considering how long they have had to implement it. Don't you think that would be a great first step forward, and that it would open up for completely new approaches to designing with CSS?
I do. So I think the first thing is to get CSS 2.1 fully implemented. How to make you-know-who do that, I have no idea.
In the meantime, some people could form the 2nd Generation CSS Samurai (http://archive.webstandards.org/css/) and write a CSS 2.2 specification in the hopes that it will be adopted, or at least put some pressure on the W3C and browser vendors.
Visit site to read or post comments… (http://www.456bereastreet.com/archive/200705/is_it_time_for_css_22/#comments)Add 456 Berea Street to your Technorati favorites. (http://technorati.com/faves?add=http://www.456bereastreet.com)
Posted in CSS (http://www.456bereastreet.com/archive/categories/css/).
http://feeds.feedburner.com/~a/456bereastreet?i=JlLyUN</img> (http://feeds.feedburner.com/~a/456bereastreet?a=JlLyUN)
http://feeds.feedburner.com/~f/456bereastreet?i=ui5lGAcY</img> (http://feeds.feedburner.com/~f/456bereastreet?a=ui5lGAcY) http://feeds.feedburner.com/~f/456bereastreet?i=rDWiF8aq</img> (http://feeds.feedburner.com/~f/456bereastreet?a=rDWiF8aq) http://feeds.feedburner.com/~f/456bereastreet?i=8GN3CfbK</img> (http://feeds.feedburner.com/~f/456bereastreet?a=8GN3CfbK)
More... (http://www.456bereastreet.com/archive/200705/is_it_time_for_css_22/)
While I agree that the W3C's process is way too slow, I don't think we can lay all the blame on the W3C. Browser vendors are a big part of the problem. Especially one of them (you-know-who).
Of course there are many neat features in CSS 3 that I would love to be able to use now, but just imagine for a moment that all browsers had full support for CSS 2.1. They really should, considering how long they have had to implement it. Don't you think that would be a great first step forward, and that it would open up for completely new approaches to designing with CSS?
I do. So I think the first thing is to get CSS 2.1 fully implemented. How to make you-know-who do that, I have no idea.
In the meantime, some people could form the 2nd Generation CSS Samurai (http://archive.webstandards.org/css/) and write a CSS 2.2 specification in the hopes that it will be adopted, or at least put some pressure on the W3C and browser vendors.
Visit site to read or post comments… (http://www.456bereastreet.com/archive/200705/is_it_time_for_css_22/#comments)Add 456 Berea Street to your Technorati favorites. (http://technorati.com/faves?add=http://www.456bereastreet.com)
Posted in CSS (http://www.456bereastreet.com/archive/categories/css/).
http://feeds.feedburner.com/~a/456bereastreet?i=JlLyUN</img> (http://feeds.feedburner.com/~a/456bereastreet?a=JlLyUN)
http://feeds.feedburner.com/~f/456bereastreet?i=ui5lGAcY</img> (http://feeds.feedburner.com/~f/456bereastreet?a=ui5lGAcY) http://feeds.feedburner.com/~f/456bereastreet?i=rDWiF8aq</img> (http://feeds.feedburner.com/~f/456bereastreet?a=rDWiF8aq) http://feeds.feedburner.com/~f/456bereastreet?i=8GN3CfbK</img> (http://feeds.feedburner.com/~f/456bereastreet?a=8GN3CfbK)
More... (http://www.456bereastreet.com/archive/200705/is_it_time_for_css_22/)