Skip to content

dbox/css-db

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CSS Features Database CSS Logo

Build Status Licensing Changelog

CSS Database is a comprehensive list of CSS features and their positions in the process of becoming implemented web standards. These positions reflect the TC39 process.

Did you come here to update the status of a CSS feature or add a new one? Quick, read our CONTRIBUTING.md.

Staging Process

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. Stable CSS features are missing in all browsers, while other CSS features developed outside the CSSWG are already behind flags in Chrome. This is too ambiguous for the web development community, and a more accountable process is desired.

Stage 0: Aspirational

> “This is a crazy idea.”

A CSS specification presented to the CSSWG by a champion within or outside the CSSWG. It should be considered highly unstable and subject to change.


Stage 1: Experimental

> “This idea might not be crazy.”

A CSS specification formally endorsed by the CSSWG. It should be considered highly unstable and subject to change.


Stage 2: Draft

> “This idea is not crazy.”

A CSS specification formally endorsed by the CSSWG and requiring implementations to move forward. It should be considered stable and subject to little change.


Stage 3: Adoption

> “This idea is becoming part of the web.”

A CSS specification formally endorsed by the CSSWG and being implemented by recognized browser vendors, possibly behind a flag. It should be considered stable and subject to little change.


Stage 4: Complete

> “This idea is part of the web.”

A CSS specification formally endorsed by the CSSWG and implemented by all recognized browser vendors.


No Stage: Unrecognized

> “I have no idea what I’m doing.”

This is any specification that has not yet been presented to the CSSWG, or that has been formally rejected or deprecated by the CSSWG.


Terminology

Recognized Browser Vendors

Recognized browser vendors include, in alphabetical order; Apple, Google, Microsoft, Mozilla, and Opera.

What is a champion?

A champion is the person responsible for advocating a new CSS feature to completion, performing the legwork necessary to ensure the concerns of interested CSSWG members are identified and incorporated into the proposal.

Releases

No releases published

Packages

No packages published

Languages

  • HTML 63.5%
  • JavaScript 24.8%
  • CSS 11.7%