(Languages: de en ru uk)
This page contains a list of all completed specifications and drafts by the CSS WG (formerly “CSS & FP WG”). If you want to follow the development of CSS3, this is the place to start. You have ideas? Contributions? See “If you want to help” on this page.
See also: Jens Meiert's index of properties.
W3C indicates the stability of specifications by a status code. The CSS working group uses the following, from least to most stable:
| Abbreviation | Full name |
|---|---|
| WD | Working Draft |
| LC | Last Call |
| CR | Candidate Recommendation |
| PR | Proposed Recommendation |
| REC | Recommendation |
The names are defined in sections 7.3 and 7.4 of the W3C process document. A REC is what is normally referred to as a “standard.” W3C encourages everyday use starting from CR.
Everybody can take part in the discussions on the archived mailing list [email protected]. You can subscribe yourself. This is the preferred place for discussions, since the members of the working group will see them. Please don't use this list for questions of the type How do I… Use comp. infosystems. www. authoring. stylesheets ("ciwas") or see “Learning CSS”.
If you work for a W3C member organization, you can also join the CSS working group and see drafts before they are published. To participate you need to commit to (on average) 1 day per week. Contact me or your organization's W3C contact person. The group's minutes are public and posted on the CSS WG blog.
A specification is not a manual. There is no excuse for badly written drafts and please complain if you find one. But specs do target a specific audience. See Elika Etemad's Understanding the CSS Specifications.. J. David Eisenberg has written another useful How to read W3C specs.
The CSS working group intends to spend a lot of time on developing the CSS test suites along with the CSS specifications. By providing a test suite for each module as soon as the module is published, we hope not only that CSS3 implementations will conform to the specification much earlier, but also that people will have an easier time understanding the formal text of the spec.
The test suites have their own archived mailing list [email protected]. Please send error reports, test case submissions, and any other questions and comments about the CSS test suites there. Elika Etemad maintains the CSS Testing Wiki with more info for contributors.
The source mark-up of the specifications follows certain conventions (which is useful for automatic processing).
