[selectors] Adding infinity loop pseudo-classes and :contains() to the snapshot profile
Open
Nobody has claimed this yet.
selectors-4
selectors-5
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
I suggest to restore the snapshot profile and add there :contains() and pseudo-classes which may cause infinity loops if detecting them really requires significant changes in browser architectures and is problematic (it is better to ask browser developers how it is for now).
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 reviewing the issue's proposal to restore the snapshot profile and add :contains() plus pseudo-classes that may cause infinite loops. Check the CSS Working Group's current snapshot-profile material and selector discussions; done would require an agreed scope and documented treatment for these selectors.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100