简体中文
EnglishCan wpt.fyi Show Browser Support for a Specific Web Feature?
Updated
Yes. wpt.fyi (the web-platform-tests dashboard) lets you look up test results for a specific web feature and compare pass rates across browsers. Search for the feature or API name, open the matching test directory or run, and read the per-browser pass/fail counts. Treat the results as evidence of test conformance, not as a formal compatibility guarantee: a feature can pass all tests in a browser and still behave differently in real pages, and a feature with thin test coverage can look healthier or worse than it is.
Finding Tests for a Feature
wpt.fyi is built on the web-platform-tests (WPT) repository, where tests are organized into directories that mirror web platform areas (for example, a directory for a given API or CSS module). To locate a feature:
- Enter the feature name, API name, or CSS property in the dashboard's search field.
- Open the test directory or individual test file that matches your target.
- Select the browser or browser channel you care about to see results for that run.
The expected result is a list of test files with per-browser status. If the search returns nothing, the feature may have no dedicated tests yet, or the tests may live under a differently named directory — try alternate names (interface name vs. spec section name) before concluding coverage is missing.
Reading the Results
Each test file shows pass and fail counts per browser. A high pass rate across browsers is a signal of interoperability; a low or uneven rate points to implementation gaps or spec ambiguity. When comparing browsers, use the same test run and the same channel (for example, stable vs. experimental) so the comparison is like-for-like. Results from experimental channels can move quickly and may not reflect what users on stable releases see.
What the Results Do and Do Not Tell You
| What wpt.fyi shows | What it does not show |
|---|---|
| Whether a browser passes specific WPT tests | Whether the feature works in every real-world scenario |
| Pass rates you can compare across browsers | A formal compatibility statement or guarantee |
| Coverage gaps when a feature has few or no tests | Feature behavior outside what the tests exercise |
A feature with full test coverage and consistent passes is a strong interoperability signal. A feature with sparse tests may show misleadingly clean results simply because little is being checked. Use the dashboard to spot where implementations diverge, then confirm behavior in the browsers you actually target.
Using It Alongside Other Resources
wpt.fyi is most useful as one input among several. Pair it with:
- MDN browser compatibility tables for a feature-level support summary and notes on known differences.
- Can I use for adoption and support context on widely used features.
- Your own testing on the browsers and versions your audience uses, especially for features where WPT coverage is thin.
If the dashboard shows a feature passing everywhere but your target browser still misbehaves, the tests likely do not cover the specific behavior you depend on — that gap is the thing to investigate next.