Centralize definition for name conflict handling of naming at-rules
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
As @cdoublev pointed out in #12973, most of the at-rules that define a name have a definition that indicates that the last one wins. Though there are currently a few at-rules like @color-profile and @font-palette-values, for which handling of duplicate names is undefined.
Therefore, I think we should establish a general term for these name-defining at-rules and centralize the definition for name conflict handling, so all those rules can refer to it.
I am not sure where that definition could live. We currently have one for at-rules in general in CSS Syntax 3, but that might not be the best place for a definition like that.
Sebastian
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 with the CSS Syntax 3 definition of at-rules and the linked CSS Color 5 and CSS Fonts 4 sections for @color-profile and @font-palette-values. Determine where a general term for name-defining at-rules belongs and how duplicate-name handling should be centralized. Done means the definition has an agreed location and the relevant rules can refer to it consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100