Skip to content

[BUG] Stylelint config enforces legacy CSS notation instead of modern standards #2779

@Rajlakshmi-ai

Description

@Rajlakshmi-ai

🐛 What's broken?

The .stylelintrc.json file explicitly configures several rules to enforce legacy CSS syntax rather than modern web standards. Specifically, "color-function-notation": "legacy" forces the use of comma-separated color values (e.g., rgba(0, 0, 0, 0.5)) instead of the modern, space-separated standard (rgb(0 0 0 / 50%)). Additionally, "media-feature-range-notation": "prefix" forces old-style media queries (min-width) over the newer context syntax (width >=).

For a modern CSS framework, this actively prevents developers from using up-to-date CSS features and syntax.


📋 Steps to Reproduce

  1. Navigate to the repository file: .stylelintrc.json.
  2. Inspect the "rules" object.
  3. Observe lines 6 and 20 where color-function-notation and media-feature-range-notation are configured.

✅ Expected Behavior

The framework should embrace modern CSS standards. color-function-notation should be set to "modern" (or removed, as "modern" is the default in stylelint-config-standard), and media-feature-range-notation should be updated to "context".


❌ Actual Behavior

The configuration forces legacy comma-separated color functions and legacy media feature prefixes.


🔗 Reproduction

Current Structure:

"color-function-notation": "legacy",
"media-feature-range-notation": "prefix",

Metadata

Metadata

Assignees

Labels

GSSoC-26Official GSSoC 2026 issueacceptedContribution approved for integration into EaseMotion CSSgood first issueGood for newcomersgssoc:approvedApproved for GSSoC contributionshelp wantedExtra attention neededlevel:intermediateRequires moderate project understandingtype:featureNew functionality or enhancement

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions