https://github.com/w3c/css-houdini-drafts

Mirror of https://hg.css-houdini.org/drafts
https://github.com/w3c/css-houdini-drafts

Last synced: about 1 month ago
JSON representation

Mirror of https://hg.css-houdini.org/drafts

• Host: GitHub
• URL: https://github.com/w3c/css-houdini-drafts
• Owner: w3c
• License: other
• Created: 2014-12-30T04:57:25.000Z (almost 10 years ago)
• Default Branch: main
• Last Pushed: 2024-08-25T01:12:03.000Z (3 months ago)
• Last Synced: 2024-09-30T07:01:39.451Z (about 1 month ago)
• Language: Bikeshed
• Homepage: https://drafts.css-houdini.org/
• Size: 4.27 MB
• Stars: 1,837
• Watchers: 184
• Forks: 141
• Open Issues: 259
• Metadata Files:
  • Readme: README.markdown
  • Contributing: CONTRIBUTING.md
  • License: LICENSE.md
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

• awesome - css-houdini-drafts - Mirror of https://hg.css-houdini.org/drafts (HTML)
• awesome-list - css-houdini-drafts - houdini.org/drafts | w3c | 1759 | (HTML)
• awesome-css - W3c/css-houdini-drafts - Mirror of Houdini WG Editor repository. (CSS Working Group / Editor's Draft :black_nib:)

README

        
### [CSS-TAG Houdini Task Force](https://wiki.css-houdini.org/) Specifications

This is the repository containing the [CSS/TAG Houdini Task Force specifications](https://drafts.css-houdini.org/). For an overview of current status, see [Is Houdini Ready Yet?](https://ishoudinireadyyet.com/)

In addition to this git repository, a Mercurial mirror is maintained at `https://hg.css-houdini.org/drafts`, if for whatever reason you prefer Mercurial.

Specification issues are raised and discussed in GitHub Issues in this repository.

We also maintain the [public-houdini mailing list](http://lists.w3.org/Archives/Public/public-houdini/) for general-interest topics.

New specifications are generally first incubated in the WICG, in particular:

- [Animation Worklet](https://github.com/WICG/animation-worklet)

# Tests

For normative changes, a corresponding

[web-platform-tests](https://github.com/web-platform-tests/wpt) PR is highly appreciated. Typically,

both PRs will be merged at the same time. Note that a test change that contradicts the spec should

not be merged before the corresponding spec change. If testing is not practical, please explain why

and if appropriate [file an issue](https://github.com/web-platform-tests/wpt/issues/new) to follow

up later. Add the `type:untestable` or `type:missing-coverage` label as appropriate.