Serialize a simple selector seems incomplete
Open
Nobody has claimed this yet.
cssom-1
selectors-3
selectors-4
selectors-5
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
In particular https://drafts.csswg.org/cssom/#serialize-a-simple-selector doesn't seem to acknowledge that the prefix can also be * and might need to be serialized at times (and not as \*). Also, it's a tad unclear that step 3 and 4 are mutually exclusive.
(This is applicable to both elements and attributes.)
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 at the CSSOM “serialize a simple selector” section linked in the issue and read steps 3 and 4 in context. Clarify their mutual exclusivity and cover the * prefix for both elements and attributes, including when it must be serialized and how it should appear. Done means the specification text unambiguously defines these cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100