projectwallace / projectwallace/css-analyzer
bring back selector browserhacks
Open
Nobody has claimed this yet.
✨ enhancement
- Dominant language
- TypeScript
- Stars
- 366
- Forks
- 15
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 3
Description
See https://github.com/projectwallace/css-selector-browser-h4cks-analyzer/blob/master/test.js for a list of selectors and tests.
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 reviewing the selector list and tests in the linked test.js from css-selector-browser-h4cks-analyzer, then locate the corresponding selector handling in this analyzer. Done means browser-hack selectors are recognized again and the referenced cases pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100