[selectors-4] Clarify the value range of pseudo selectors
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- css
- Domain
- documentation
Research direction
Locate the source for § Grammar and review the linked sections on pseudo-elements, invalid selectors, partial implementations, and Web Compat. Add a clarifying note covering the intended open value range and invalid unsupported pseudos, then build the specification and check that the links and wording render correctly.
Written by the indexing model from the issue text.
Description
§ Grammar defines pseudos with a relatively open range of values that does not come with any restriction, at least not within reasonable reading proximity.
§ Pseudo-elements says that pseudos are defined by CSS specifications and the host language.
§ Invalid Selectors says that UAs must treat as invalid any pseudos for which they have no usable level of support. But in a non-normative note, as reported in #8305. § Appendix B: [...] Web Compat adds an exception: UAs must support ::webkit-unknown even if they have no support for it.
A note similar to the one below could be added in § Grammar:
The
<pseudo-element-selector>and<pseudo-class-selector>productions are intentionally open to represent any pseudo-class and pseudo-element defined in CSS specifications or by the host language, that is supported by the UA. As per Patial implementations, other pseudos are otherwise invalid, unless otherwise specified (like in § Appendix B: [...] Web Compat).
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 24
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.
More from w3c/csswg-drafts
-
Agenda+ css-sizing-4 css-values-5
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
w3c/csswg-drafts#14502 · 1 reaction ·
-
css-values-5 editorial Needs Edits
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
w3c/csswg-drafts#14498 · 2 comments ·
-
css-overflow-4 topic: line-clamp
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
w3c/csswg-drafts#14485 · 1 comment ·
-
Administrative Tracker css-values-4
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
w3c/csswg-drafts#14482 · 4 comments · 1 reaction ·
-
css-values-5 Needs Edits
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
w3c/csswg-drafts#14466 ·
All issues in w3c/csswg-drafts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bancolombia/sentinel#22 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
redhat-developer/rhdh-plugins#4887 · 2 comments ·