w3c / w3c/css-validator

CSS checker request for enhancement; scanning the contents of @imports should be an option

Open
#490 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
250
Forks
123
PR merge metrics
No merged PRs in 30d

Description

The CSS checker scanning the contents of @imports should be an option; a tickbox when you start your scan.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named in the issue. Start at the CSS checker’s scan configuration and the code that handles @imports; determine where an option can be exposed when a scan starts. Done means users can choose whether imported content is scanned and the selected behavior is honored.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, java
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.