CSS Database is a comprehensive list of CSS features and their positions in the process of becoming implemented web standards.
Did you come here to update the status of a CSS feature or add a new one? Quick, read our CONTRIBUTING.md.
Staging processes allow developers to accomplish real things and get involved in the creation of standards, testing, feedback, and new use cases.
This staging process reflects the real-life stability of new CSS features.
You can read an inside view of the CSSWG to learn about the official (and unofficial) development stages of CSS specifications. In reality, specifications and browser implementations happen out of sync. For example, there are stable CSS features missing in all browsers, while other CSS features developed outside the CSSWG have appeared in browsers behind flags. This is too ambiguous for the web development community, and a more accountable process is desired.
“This is my crazy idea.”
An Editor’s Draft championed by a non-CSSWG member. It should be considered highly unstable and subject to change.
“This is a crazy idea.”
An Editor’s Draft championed by a CSSWG member. It should still be considered highly unstable and subject to change.
“This idea might not be crazy.”
An Editor’s Draft hosted by the CSSWG or W3C. It should still be considered highly unstable and subject to change.
“This idea is not crazy.”
A Working Draft hosted by the CSSWG or W3C and requiring implementations to move forward. It should be considered stable and subject to little change. It is still subject to rejection as a standard.
“This idea is becoming part of the web.”
A Candidate Recommendation hosted by the CSSWG or W3C and being implemented by at least 2 recognized browser vendors, possibly behind a flag. It should be considered stable and subject to little change. It will likely become a standard.
“This idea is part of the web.”
A Recommendation hosted by the CSSWG or W3C and implemented by all recognized browser vendors. It is a standard.
“I had no idea what I was doing.”
This is any specification that has been rejected or neglected by its editor, or formally rejected by the CSSWG.
Recognized browser vendors include, in alphabetical order; Apple, Google, Microsoft, Mozilla, and Opera.
A champion is the person responsible for advocating a new feature to completion, performing the legwork necessary to ensure the concerns of interested parties are identified and incorporated into the proposal. Once the CSSWG hosts the draft for a feature, its champion is recognized as the organization itself.