[css-selectors] Standardise `:(‑moz‑)first‑node` and `:(‑moz‑)last‑node`
Open
Nobody has claimed this yet.
selectors-5
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Right now, CSS Selectors 4 defines :first-child and :last-child, which works as such for the following:
span:last-child {
background-color: lime;
}
<div>
<span>This doesn’t match.</span>
<span>This matches.</span>
</div>
<div>
<span>This matches.</span>
Some text after.
</div>
For :first-node and :last-node, this would work as follows:
span:last-node {
background-color: lime;
}
<div>
<span>This doesn’t match.</span>
<span>This matches.</span>
<!-- White-space and comments are ignored when
- determining whether :last-node matches -->
</div>
<div>
<span>This doesn’t match.</span>
Some text after.
</div>
Mozilla Firefox already implements the previous in prefixed form and exposes it to the web.
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 Selectors 4 child-index section and the linked MDN documentation for :first-child, :last-child, :first-node, and :last-node. Compare the issue’s HTML and CSS examples with Firefox’s prefixed behavior; done means the standard treatment of the selectors and their prefixed forms is clearly resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100