…CSS Working Group is not an innovation body, it’s a standards body who’s job it is to standardise browser makers’ implementations of CSS.
I never said the working group was creating these proposals.
When the W3C can see commonality in various browser maker implementations, then it is on it’s way to being a standard, not the other way around.
That’s certainly not true in every case, there have been many proposals that have become candidate recommendations before any other browser have implemented them e.g. The File API.
In the case of CSS transitions & animations these initial proposals have gone through rounds of discussion on the w3c mailing lists to become working drafts. Again before any non webkit based browser has implemented them.
I would appreciate anyone more familiar with the process to weigh in if I am mistaken.
Ryan Seddon
@Andy Clarke
I never said the working group was creating these proposals.
That’s certainly not true in every case, there have been many proposals that have become candidate recommendations before any other browser have implemented them e.g. The File API.
In the case of CSS transitions & animations these initial proposals have gone through rounds of discussion on the w3c mailing lists to become working drafts. Again before any non webkit based browser has implemented them.
I would appreciate anyone more familiar with the process to weigh in if I am mistaken.