There is a css standard document comming. And there is a discussing where people agreed to put css in alphabetical order. With some minor exceptions for border and shadow browser specific elements.

.selector {
background: green;
-moz-border:0;
-webkit-border:0;
border: 0;
padding: 0;
...
}

It would be nice if we could do that with Bartik before it goes into core, that why we won't have to patch it afterwards.
I don't have a lot of time these days, so I won't be able to do it today or tomorow.

Comments

jensimmons’s picture

jensimmons commented
Status: Active » Closed (won't fix)

Yeah, we aren't going to do this. The Drupal CSS coding standards are not finalized. There is an ongoing debate about whether selectors should go in alphabetical order or in box-model order (from outside to inside order / from big effect to small effect). I'm firmly in the camp that believes the order should be logical, not alphabetical.

We are also deviating from the proposed standard in several ways: by putting hex colors in lowercase, not putting an extra space between every declaration, and not using php-style format for comments. Instead we are using very popular CSS coding standards that are using over and over throughout the webstandards community.

The CSS coding standards debate in the Drupal community is going to take a while. It's been going on for almost two years, and many significant front-end development and design leaders in the Drupal community have strong disagreements with what's being proposed.

geerlingguy’s picture

geerlingguy commented
Issue summary: View changes
Issue tags: +Bikeshed

Not calling anyone out, or anything like that (I was on the side of the alphabetical purists, for no rational reason!)... just wanted to add this tag for potential future examples.