mdn / mdn/browser-compat-data

css.at-rules.supports.at-rule - missing compat data for @supports at-rule()

Open Beginner friendly
#29,549 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:multiple data:css info needed
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

BCD has data for @supports in css/at-rules/supports.json, including subfeatures for selector(), font-tech(), and font-format().

It does not currently have data for the new at-rule() support condition function used inside @supports, for example:

@supports at-rule(@starting-style) {}

Proposed BCD path: css.at-rules.supports.at-rule

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet)

What did you expect to see?

I expected BCD to have a subfeature under css.at-rules.supports for the at-rule() support condition function, similar to the existing selector(), font-tech(), and font-format() subfeatures.

Did you test this? If so, how?

I checked the current BCD source file:
https://github.com/mdn/browser-compat-data/blob/main/css/at-rules/supports.json

WPT:
https://github.com/web-platform-tests/wpt/blob/master/css/css-conditional/js/supports-at-rule.html

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?
MDN URL

No response

MDN metadata

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open css/at-rules/supports.json and compare the existing selector(), font-tech(), and font-format() subfeatures. Use the linked WPT supports-at-rule.html and the reported browser versions to add the at-rule() compatibility entry at css.at-rules.supports.at-rule. Done means the data matches the proposed path and passes the repository's validation checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.