We're really happy to accept contributions to the mdn/browser-compat-data repository!
- Before you begin
- Ways to contribute
- Finding browser version numbers for features
- Updating compatibility tables on MDN
- Opening issues and pull requests
- Getting help
The browser-compat-data project (BCD) welcomes contributors of all kinds, but we ask that you keep these guidelines in mind when you're contributing.
The project requires that all contributors follow Mozilla's code of conduct and etiquette guidelines.
This project has a formal governance document, which describes how various types of contributors work within the project and how decisions are made.
The repository is made available under the terms the Creative Commons CC0 Public Domain Dedication. Any contributions must be compatible with its terms. If you're not sure about that, please ask.
There are many ways you can help improve this repository! For example:
- Add new compat data: familiarize yourself with the schema and read the schema docs and data guidelines to add new files.
- Fix existing compat data: maybe a browser now supports a certain feature. Yay! If you open a PR to fix a browser's data, it would be most helpful if you include a link to a bug report or similar so that we can double-check the good news.
- Fix a bug: we have a list of issues, or maybe you found your own.
- Review a pull request: there is a list of PRs. Let us know if these look good to you.
When adding data for a particular feature, you'll often need to find which version of each browser the feature first shipped in. For how-to guidance which will help you do that, see Matching web features to browser release version numbers.
It takes up to four weeks for BCD changes to be reflected in MDN's browser compatibility tables. The process is:
-
A pull request is reviewed and merged to
main. -
Project owners publish a new release of
@mdn/browser-compat-data. See Publishing a new version of@mdn/browser-compat-datafor details. -
MDN staff build and deploy a new image of Kumascript, which includes the BCD release, to production. This typically happens within a day of the release of the npm package.
-
Tables are generated on MDN:
- Existing tables automatically regenerate monthly. Alternatively, logged-in MDN users can force-refresh a page to regenerate it.
- For new pages, you must add the
{{Compat}}macro to the page. For instructions, see Inserting the data into MDN pages.
Large-scale changes follow a different process. See Migrations for details.
Before submitting your pull request, validate your new data against the schema.
Not everything is enforced or validated by the schema. A few things to pay attention to:
- Feature identifiers (the data namespaces, like
css.properties.background) should make sense and are spelled correctly. - Nesting of feature identifiers should make sense.
- Notes use correct grammar and spelling. They should be complete sentences ending with a period.
If the feature you're interested in is a JavaScript API, you can cross-reference data against Web API Confluence using the confluence command. This command overwrites data in your current working tree according to data from the dashboard. See Using Confluence for instructions.
If the feature you're interested in is an API, CSS or JavaScript feature, you can cross-reference data against mdn-bcd-collector. See the project's guide on updating BCD using the results for instructions.
Many browsers within BCD can be derived from other browsers given they share the same engine, for example Opera derives from Chrome, and Firefox Android derives from Firefox. To help cut down time working on copying values between browsers, a mirroring script is provided. You can run npm run mirror <browser> <feature_or_file> -- [--source=""] [--modify="nonreal"] [--target_version=""] to automatically copy values.
The argument is the destination browser that values will be copied to. The script automatically determines what browser to copy from based upon the destination (see table below).
| Destination | Default Source |
|---|---|
| Chrome Android | Chrome |
| Edge | Chrome |
| Firefox Android | Firefox |
| Opera | Chrome |
| Opera Android | Chrome Android |
| Safari iOS | Safari |
| Samsung Internet | Chrome Android |
| WebView | Chrome Android |
The <feature_or_filename> argument is either the identifier of the feature to update (i.e. css.at-rules.namespace), a filename (javascript/operators/arithmetic.json), or an entire folder (api).
Note when using feature identifiers:
- Updates aren't applied recursively; only the given data point is updated when using a feature ID. Use a filename or folder for mass mirroring.
- The script assumes a predictable file structure when passing in a feature identifier, which BCD doesn't have right now. (See issue 3617.) For example, even if "html.elements.input.input-button" is a valid query, it will fail because the file structure for input-button isn't consistent with the rest right now.
By default, the mirroring script will only overwrite values in the destination that are true or null, but can take a --modify (or -m) argument to specify whether to overwrite values that are false as well (--modify=bool), or any values (--modify=always).
The script can also take a --target_version (or -t) argument to only perform mirroring if the data affects a specific browser release. This is used to update data when a new Opera or Opera Android version is released, and we wish to update data that only affects the new version.
If you need help with this repository or have any questions, contact the MDN team on chat.mozilla.org#mdn or write to us on Discourse.