w3c / w3c/csswg-drafts

[Feature request] Support for single line comments

Open
#7,115 2 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-syntax-3
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

Doing /* */ is NOT ergonomic especially for quick prototyping, // comments are an affordance that is provided by most languages out there, including Javascript.
It's 2022 and I think this is a relatively high impact ergonomy wise, low complexity feature and therefore a low hanging fruit regarding developper experience.
Sure there might or not be some syntax edge cases, but I'm sure requiring e.g to be a space or a newline before the // would filter such exceptions (background-url) and/or by requiring to be a space after the //
There are many other possible resolution strategies.
One could look at how SCSS does it: https://sass-lang.com/documentation/syntax/comments#in-scss
Please, make it happen :)

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

Start with the requested support for // comments and compare the SCSS comment behavior linked in the issue. Determine how comment markers would interact with cases such as background-url and whether whitespace rules are needed. Done means an agreed syntax and corresponding CSS specification or editor-draft change, with edge cases resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, scss
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.