Browsercompat Get Feature
browsercompat_get_featureRead-onlyIdempotent
Get the compatibility record for one web feature: Baseline state and the date it crossed, deprecation and standards status, per-browser version added and removed with flags, vendor prefixes and partial-implementation notes — with every other support statement recorded for that browser, such as an earlier prefixed or flagged release, in other_statements — and the MDN and specification links. Accepts a BCD key such as css.selectors.has or a web-features id such as has; the response echoes which one it matched. A web-features id that spans several BCD keys, such as grid, returns web-features’ own feature-level release per Baseline core browser in feature_support and its compat_keys, 100 per page, in place of per-key fields. An unresolved feature returns found: false with guidance rather than an error.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| feature | Yes | A browser-compat-data key such as css.selectors.has, or a web-features id such as has, 1 to 200 characters. An empty or longer string is rejected against this schema; a whitespace-only string returns invalid_feature_input. Call browsercompat_search_features first if you do not already know the key. | |
| resolve | No | When true, a string that is neither a key nor an id falls back to the search index, such as "Container queries (size)" or "Element.prototype.animate". Its best exact matches are accepted only when they name one feature: a single key resolves to that key, several keys of one web-features feature resolve to the feature with its feature_support and compat_keys, and matches spanning two features are a miss. Off by default so a typo returns a miss you can correct rather than a confident answer about the wrong feature. | |
| subkeys_offset | No | Direct child keys to skip, default 0. Each subkeys page contains at most 100 keys; pass its next_offset to continue. | |
| include_runtimes | No | Add the bun, deno, nodejs, and oculus rows to support. Leave off for browser ship decisions. | |
| compat_keys_offset | No | compat_keys to skip, default 0, for a web-features id that spans several keys. Each page of compat_keys holds at most 100; pass compat_keys_next_offset to continue. Has no effect when the feature resolves to a single key. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | web-features display name for the feature. | |
| error | No | Present when the call failed. Absent on success. | |
| found | No | True when the feature string resolved to a tracked entry. | |
| status | No | Standards status for the resolved key. Absent for webextensions keys, which record none, and when the id spans more than one key. | |
| mdn_url | No | MDN reference page for the resolved key. | |
| outcome | No | found when per-feature data was returned, no_compat_data when the entry is tracked but owns no browser-compat-data keys, miss when nothing matched. | |
| subkeys | No | Direct child compat records of the resolved BCD key. Absent for childless keys and resolutions without a single key. | |
| support | No | One row per reported browser, judged at its newest shipped release, with the other statements recorded for that browser in other_statements. Absent when the id spans more than one browser-compat-data key; feature_support covers that case. | |
| baseline | No | Baseline state for the resolved key, or the feature rollup when a web-features id resolved to more than one key. | |
| guidance | No | What to do next on a miss or with no compat data. | |
| spec_urls | No | Specification URLs for the resolved key, always an array. | |
| compat_keys | No | Present when the web-features id spans more than one browser-compat-data key, or as an empty list when it owns none: at most 100 of its keys in declaration order, starting at compat_keys_offset. Call this tool again with one of them for the per-key support, status, and links. | |
| description | No | web-features description, or the browser-compat-data description with tags stripped. | |
| discouraged | No | Feature-level discouragement, independent of leaf standards status. Also retained in status.discouraged when status exists. | |
| resolved_as | No | How the feature string was matched, or null on a miss. | |
| data_version | No | Vintage of each bundled dataset behind this answer. | |
| feature_support | No | Present only when the web-features id spans more than one browser-compat-data key: one row per Baseline core browser with the release web-features lists for the feature as a whole, the data its feature-level Baseline is computed from. It is web-features’ answer for the feature, not a combination of its keys, and a key can differ from it either way — a lists Chrome 1 while one of its keys is unsupported, and anchor-positioning lists no Chrome release though most of its keys are supported there. Call this tool with one of compat_keys for a key-level answer. Non-core browsers are not covered. | |
| limiting_browser | No | Among the Baseline core browsers, the one whose required release is newest by release date. For a single key, present only when every core browser has full, unprefixed, unflagged support at a resolvable added release; for an id spanning more than one key, read from feature_support and present only when it lists all seven core browsers. | |
| runtimesExcluded | No | Notes that the feature carries server-runtime or XR data that was left out. | |
| baselineNotMapped | No | Explains why a resolved key carries no Baseline state. | |
| compat_keys_total | No | Every browser-compat-data key the id owns, before paging. Present with compat_keys. | |
| compat_keys_next_offset | No | compat_keys_offset for the next page of compat_keys; absent at or past the end. |