Missing data: container query features
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
Unlike media queries, container query features aren't tracked by BCD. For example, there's a feature for the media query feature aspect-ratio (css.at-rules.media.aspect-ratio), but there are no corresponding features for container queries (e.g., I'd expect there to exist css.at-rules.container.aspect-ratio).
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
I'd expect features for these container query features:
- width
- height
- inline-size
- block-size
- aspect-ratio
- orientation
- scroll-state: stuck
- scroll-state: snapped
- scroll-state: scrollable
Tracking scroll states individually would be helpful in the case that further states are added (https://github.com/w3c/csswg-drafts/issues/6400,
https://github.com/w3c/csswg-drafts/issues/11191).
Did you test this? If so, how?
I have not tested this.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
Prompted by https://github.com/web-platform-dx/web-features/pull/2567/
Do you have anything more you want to share?
No response
MDN URL
No response
MDN metadata
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing css.at-rules.media.aspect-ratio entry and the web-platform-dx/web-features pull request 2567 first. Compare the requested container-query and scroll-state features with the repository's existing data structure and contribution guidance. Done means the requested features are represented with valid compatibility data and schema checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- data, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100