[css-page-3] Allow custom property declarations in `@page` and margin rules
Open
Nobody has claimed this yet.
css-page-3
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Chrome/FF (at least) allows custom properties in @page and margin rules although this is not allowed by CSS Paged Media 3. CSS Anchor Position 1 does not allow them in @try.
But I cannot think of a valid reason to exclude them.
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 CSS Paged Media 3 rules for @page and margin rules, then compare the CSS Anchor Position 1 treatment of custom properties in @try. Determine whether the specifications should permit these declarations and update the relevant editor-draft text if agreed; done means the allowance is consistently specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100