Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit

This reverts commit fc365dddd74a2c9ba22036fd5563dbea8ff34c7c.

Reason for revert: failures of external/wpt/css/css-values/signs-abs-computed.html on at least

Original change's description:
> Check if math expression has percentages deep inside
> Currently, only the top level category is checked to have a percentage
> dependency, check all the nodes inside the expression as well,
> as it can be the case like:
> NumberProducingFunction(Percentage) * Pixels.
> The top level category is Length in such case and we try to resolve it
> with ComputeLength, where percentages are not allowed.
> Note: the added test would crash before the CL, as it would try to
> GetDouble() of percentage which is not allowed in that context.
> Bug: 1505817
> Change-Id: Iefd13c0d190c3b8adf463ea244f81331635e14fe
> Reviewed-on:
> Commit-Queue: Daniil Sakhapov <>
> Reviewed-by: Anders Hartvoll Ruud <>
> Cr-Commit-Position: refs/heads/main@{#1230671}

Bug: 1505817
Change-Id: I8ce6bd91c3b69cdbb6036d3ad73b08c200447ea7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Owners-Override: David Baron <>
Auto-Submit: David Baron <>
Commit-Queue: Rubber Stamper <>
Bot-Commit: Rubber Stamper <>
Cr-Commit-Position: refs/heads/main@{#1230704}


Failed to load latest commit information.
Latest commit message
Commit time

The web-platform-tests Project

Taskcluster CI Status documentation manifest Python 3

The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.

The most important sources of information and activity are:

  • the canonical location of the project's source code revision history and the discussion forum for changes to the code
  • the documentation website; details how to set up the project, how to write tests, how to give and receive peer review, how to serve as an administrator, and more
  • a public deployment of the test suite, allowing anyone to run the tests by visiting from an Internet-enabled browser of their choice
  • an archive of test results collected from an array of web browsers on a regular basis
  • Real-time chat room: the matrix channel; includes participants located around the world, but busiest during the European working day.
  • Mailing list: a public and low-traffic discussion list
  • RFCs: a repo for requesting comments on substantial changes that would impact other stakeholders or users; people who work on WPT infra are encouraged to watch the repo.

If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.

Setting Up the Repo

Clone or otherwise get

Note: because of the frequent creation and deletion of branches in this repo, it is recommended to "prune" stale branches when fetching updates, i.e. use git pull --prune (or git fetch -p && git merge).

Running the Tests

See the documentation website and in particular the system setup for running tests locally.

Command Line Tools

The wpt command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:

  • wpt serve - For starting the wpt http server
  • wpt run - For running tests in a browser
  • wpt lint - For running the lint against all tests
  • wpt manifest - For updating or generating a MANIFEST.json test manifest
  • wpt install - For installing the latest release of a browser or webdriver server on the local machine.
  • wpt serve-wave - For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.

Windows Notes

On Windows wpt commands must be prefixed with python or the path to the python binary (if python is not in your %PATH%).

python wpt [command]

Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt commands.

Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false in your working tree.


The master branch is automatically synced to and


Save the Web, Write Some Tests!

Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.

The way to contribute is just as usual:

  • Fork this repository (and make sure you're still relatively in sync with it if you forked a while ago).
  • Create a branch for your changes: git checkout -b topic.
  • Make your changes.
  • Run ./wpt lint as described above.
  • Commit locally and push that to your repo.
  • Create a pull request based on the above.

Issues with web-platform-tests

If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!