microsoft / microsoft/vscode-css-languageservice
[SCSS] Specificity values for nested rules are incorrect
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 384
- Forks
- 217
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 14
Description
Discovered this issue while working on #249
input { #id { p { color: red; } } } - Specificity (0, 0, 1)
input #id p { color: red; } - Specificity (1, 0, 2)
Even though they are equivalent
Contributor guide
No contributing guide indexed for this repository
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 reproducing the nested SCSS example and comparing its reported specificity with the equivalent flat selector in the CSS language service. Trace how specificity is calculated for nested rules; done means both equivalent forms report (1, 0, 2).
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scss, typescript
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100