Add standardized prefixed APIs as separate entries?
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
In https://github.com/web-platform-dx/web-features/pull/977#pullrequestreview-2028097234 @ddbeck said:
Honestly, I do not love the change in https://github.com/mdn/browser-compat-data/pull/22951. It seems to me that spec'd prefixes ought to be their own keys in BCD (i.e., we ought to have both
css.properties.-webkit-line-clampandcss.properties.line-clamp), since in a lot of ways it's more like a shorthand than a prefix.
Should we do this?
CC owners @Elchi3 @Rumyra @queengooborg
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
Start by reading the linked web-platform-dx PR #977 and the browser-compat-data PR #22951, including the referenced review comment. Determine whether spec-defined prefixes should be represented as separate BCD keys; the work is complete only when the project agrees on that data-model decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100