title: why is css longhand equivalent usefull
body: <p>I was looking for a grunt tool to parse my css and tell me when I can convert longhand css properties to shorthand. My way of thinking that this makes css smaller, easier to understand.</p>
  
  <p>So basically if it will find </p>
  
  <pre><code>.mydiv{
    background-color: #000;
    background-image: url(images/bg.gif);
    background-repeat: no-repeat;
    background-position: top right;
    font-style: italic;
    font-weight: bold;
    font-size: .8em;
    line-height: 1.2;
    font-family: Arial, sans-serif;
  }
  </code></pre>
  
  <p>It would change it to:</p>
  
  <pre><code>.mydiv{
    background: #000 url(images/bg.gif) no-repeat top right;
    font: italic bold .8em/1.2 Arial, sans-serif;
  }
  </code></pre>
  
  <p>To my surprise I was not able to find such plugin, but on the other side I found a lot of them which convert shorthand properties to longhand. This raised a question: </p>
  
  <p><strong>why do people want to convert their nice and clean shorthand equivalents to longhand?</strong> is there any valid reason except:</p>
  
  <ul>
  <li>I like it to be longer</li>
  <li>some really outdated browser like IE 7 screws up something. (by outdated I mean IE &lt;=7, chrome, ff, safari 2 versions lower then current)</li>
  </ul>
  
  <p><strong>P.S.</strong> also I am not asking for a grunt plugin, if someone knows one, please let me know.</p>
  
  <p><strong>P.P.S</strong> I saw <a href="https://stackoverflow.com/questions/5959652/css-shorthand-vs-longhand">this question</a> and the person is concerned with: performance and documentation. I do not care about these things because: people in my team can read and understand shorthand and prefer it, and I know that performancewise (for parsing rules) it makes really tiny difference (if any) and it is smaller in case of bandwidth.</p>
  
  <p>What I am concerned is that may be I will get different representations in some browsers.</p>