Logical properties missing computed values
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 787
- Forks
- 216
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 6
Description
This is basically a follow question up to a comment in [#319](https://github.com/mdn/data/pull/319#issuecomment-435011101): some logical shorthands miss a computed property, because at the time it wasn't clear what those would be. My question is, is this something that can/should be fixed?
The reason I'm wondering is because [csstype](https://github.com/frenic/csstype) uses the computed property as an [indicator for shorthands](https://github.com/frenic/csstype/blob/1bb6cbb1f3e55220952caa52e6f37c54b4a50f54/src/collections/syntaxes.ts#L21), which causes an issue here.
List of shorthands with missing computed list:
- inset
- inset-block
- inset-inline
- margin-block
- margin-inline
- padding-block
- padding-inline
- scroll-margin
- scroll-margin-block
- scroll-margin-inline
- scroll-padding
- scroll-padding-block
- scroll-padding-inline
- scroll-margin
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 entries for the listed logical shorthands and compare their computed-property conventions with the discussion in #319 and the linked csstype syntax reference. Determine whether the missing computed values should be added consistently across the list; the issue is complete when that decision is reflected in the affected data and the repository's existing checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100