/compat

Compatibility Standard
  1. HTML 98.8%
  2. Makefile 1.2%
HTML Makefile
Clone or download

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Download ZIP
Find file
Switch branches/tags
Nothing to show
Latest commit b1be88d Jan 8, 2018
@annevk
annevk Meta: reference whatwg/meta resources 
Also remove leftover CC0 reference.

Helps with whatwg/meta#65.
Permalink
Failed to load latest commit information.
.editorconfig Meta: enable PR preview and add editor config Feb 21, 2017
.gitattributes Meta: enable PR preview and add editor config Feb 21, 2017
.gitignore Meta: remove Node.js dependency (#92) Jan 3, 2018
.pr-preview.json Meta: enable PR preview and add editor config Feb 21, 2017
.travis.yml Meta: reference whatwg/meta resources Jan 8, 2018
CONTRIBUTING.md Meta: reference whatwg/meta resources Jan 8, 2018
LICENSE Meta: use new WHATWG boilerplate and license Jan 5, 2018
Makefile Meta: fix the README about local deploy to actually work Nov 15, 2017
README.md Meta: reference whatwg/meta resources Jan 8, 2018
compatibility.bs Meta: use new WHATWG boilerplate and license Jan 5, 2018
deploy_key.enc Meta: enable snapshots Jan 13, 2017
stroked-text.png Meta: stop referencing external image Jan 12, 2017

README.md

Compatibility Standard

Travis Build Status

Abstract

The Compatibility Standard describes a collection of non-standard (and often vendor-prefixed) CSS properties and DOM APIs that web browsers need to support for compatibility with the de facto web.

Code of conduct

We are committed to providing a friendly, safe and welcoming environment for all. Please read and respect the WHATWG Code of Conduct.

Contribute

In short, change compatibility.bs and submit your patch, with a good commit message. Consider reading through the WHATWG FAQ if you are new here.

Please add your name to the Acknowledgments section in your first pull request, even for trivial fixes. The names are sorted lexicographically.

If you want to preview the spec locally, you can either use a locally installed copy of Bikeshed by running make or use the HTTP API version by running make remote.

If you want to do a complete "local deploy" including commit and/or branch snapshots, run

make deploy

Note that this still requires access to the network.

Run bikeshed watch to enable fancy-mode (which sets up a watcher and auto-rebuilds the spec every time it changes).