Is it bad practice to comment out single lines of CSS with //?

W3C: CSS 2.1 working draft: comment characters.
W3C: CSS syntax module level 3: railroad diagrams of parser-to-character interpretations.
Stack Overflow: Various Stack Overflow articles with practically the same subject as this one.
w3schools: CSS 3 syntax standard (which in turn references W3C).
sitepoint: CSS syntax annotation on "not using double-slash".
mozilla|mdn: relaxed CSS 3 processing allows double slash in input files.

前端未结

关注

 11  1713

梦如初夏 2020-12-01 02:45

I have recently started using // to \"comment\" out single lines of CSS code. I understand that I am not actually commenting out the line; I am just breaking it

11条回答

抹茶落季 (楼主)

2020-12-01 03:03

I see that there were/are lots of people complaining about this and since this is an older question, there is probably a lot of people reading it wondering if it is still true, or if there is actually a standard in the first place. Allow me to clear the air. The following are the core reasons for the strict CSS comment policy:

#1 It is not standard

Standardized at least since CSS 2.1, comments are to ONLY be encased in /* and */. While some browsers tolerate //, they aren't supposed to, and are only one inch from someone saying "oh yeah that's non-standard" or "hey! That's non-standard, fix it!"; and then guess what, your CSS code, which WAS working, now doesn't for thousands of people (and may have already not been working for hundreds of others). I will add that are allowed but only (and I mean ONLY) when they appear within an HTML document, not in a .css source file. If your browser is so old that it can't skip over

Is it bad practice to comment out single lines of CSS with //?

#1 It is not standard