| [6a3a178] | 1 | # cssdb [<img src="https://cssdb.org/cssdb.svg" alt="cssdb logo" width="90" height="90" align="right">][cssdb]
|
|---|
| 2 |
|
|---|
| 3 | [![NPM Version][npm-img]][npm-url]
|
|---|
| 4 | [![Build Status][cli-img]][cli-url]
|
|---|
| 5 |
|
|---|
| 6 | [cssdb] is a comprehensive list of CSS features and their positions in
|
|---|
| 7 | the process of becoming implemented web standards.
|
|---|
| 8 |
|
|---|
| 9 | ---
|
|---|
| 10 |
|
|---|
| 11 | Did you come here to update the status of a CSS feature or add a new one?
|
|---|
| 12 | Quick, read [CONTRIBUTING.md](CONTRIBUTING.md).
|
|---|
| 13 |
|
|---|
| 14 | Did you come here to learn about the stages? Quick, read [STAGES.md](STAGES.md).
|
|---|
| 15 |
|
|---|
| 16 | ---
|
|---|
| 17 |
|
|---|
| 18 | [cssdb] ranks CSS features by stages that reflect the real-life stability of
|
|---|
| 19 | new CSS features.
|
|---|
| 20 |
|
|---|
| 21 | You can read an [inside view of the CSSWG] to learn about the official
|
|---|
| 22 | (and unofficial) development stages of CSS specifications. In reality,
|
|---|
| 23 | specifications and browser implementations happen out of sync. For example,
|
|---|
| 24 | there are stable CSS features missing in all browsers, while other CSS features
|
|---|
| 25 | developed outside the [CSSWG] have appeared in browsers behind flags. This is
|
|---|
| 26 | too ambiguous for the web development community, and a more accountable process
|
|---|
| 27 | is desired.
|
|---|
| 28 |
|
|---|
| 29 | [cli-img]: https://img.shields.io/travis/csstools/cssdb.svg
|
|---|
| 30 | [cli-url]: https://travis-ci.org/csstools/cssdb
|
|---|
| 31 | [cssdb]: https://github.com/csstools/cssdb
|
|---|
| 32 | [CSSWG]: https://wiki.csswg.org/spec
|
|---|
| 33 | [inside view of the CSSWG]: http://fantasai.inkedblade.net/weblog/2011/inside-csswg/process
|
|---|
| 34 | [npm-img]: https://img.shields.io/npm/v/cssdb.svg
|
|---|
| 35 | [npm-url]: https://www.npmjs.com/package/cssdb
|
|---|
