Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

These days, CSS usually refers to CSS2+. So, I suggest to map to .

I tried it myself...:

Suggest a css synonym: css2  Suggest   Failed to propose synonym: Version specific synonyms can only be created by moderators (click on this box to dismiss)

share|improve this question

closed as off-topic by CRABOLO, gnat, Ilmari Karonen, Doorknob, 3ventic Jan 12 '15 at 23:16

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – CRABOLO, gnat, Ilmari Karonen, Doorknob, 3ventic
If this question can be reworded to fit the rules in the help center, please edit the question.

But then how can you use [css2] to indicate that you are not asking about css3? – shanethehat Apr 16 '12 at 11:31
I actually think this is a good idea. css2 doesn't mean anything useful on Stack Overflow. It's usually (ab)used to mean "I need this to work in older browsers such as IE7". However, IE7 supports even some CSS3, for example ~ and overflow-y. There are currently 61 questions tagged css2, and I think it could be removed from every question. Only this question arguably needs it, but the question still makes perfect sense without it. – thirtydot Apr 17 '12 at 11:11
up vote 8 down vote accepted

I'm not sure this is a good idea. We have the tag to talk about the general field of .NET, as well as version-specific tags (such as ) for items that are specific (or more likely, introduced) in that specific version.

The tags are no different. There are times when you are speaking about CSS in general (or, the version that is most prevalent/widely-adopted at the time), but there are times when you want to speak about a specific version; this situation is when something isn't fully baked/just released so you can differentiate the technologies when an influx of new questions are going to come in on that new technology.

Going back and removing the version-specific tags (you're suggesting that is version one and that it be merged into version two) generally isn't a good idea. If anything, there might be people still using the old technology (depending on what we're talking about), and still need to differentiate between the two.

share|improve this answer
this makes sense – Wh1T3h4Ck5 Apr 16 '12 at 13:24

Not the answer you're looking for? Browse other questions tagged .