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.
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 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.
About Author :
authorUrl : http://www.456bereastreet.com/archive/200705/is_it_time_for_css_22/
To read more articles on: designer, features, developer, CSS 2.2 , specification
View more blogs here : http://www.technoinfonet.com/Blogs
No comments:
Post a Comment