I'm a minimalist when it comes to coding. I loved the idea of shorthand properties when they came out for CSS. And the dismissal of the annoying <doctype> instruction with HTML 5 release.

Anyhow, in the good moral ethics of front-end coding, is it good "juju" to declare all border properties to be the same within CSS styling, and then, right after a semicolon, subtracting a particular border property?

such as:

border: solid 1px black; border-bottom:none;

You are better off dropping it down a line for "readability"

But if you really wanted to you could put the entire ruleset on a single line with no spaces at all.

I just thought it better to code it that way rather than write the same attributes 3 different times for (left,top,right)-border.

I'm guessing that evan if you use "border: solid 1px black;" to set all four borders simultaneously, at some point the browser will still have to interpret that and set the value for all four sides one at a time. So, using your example the browser would have to do one extra assignment, meaning slighly longer execution time.

Although, with your example there will obviously also be less text and thereby a slightly smaller file to send over the net.

However, the gains of either case is too small to make any practical difference. So just go with the one you find most aesthetically pleasing

Originally Posted by MattCoops

I just thought it better to code it that way rather than write the same attributes 3 different times for (left,top,right)-border.

Sure but what I was meaning was:

.class {
     border: solid 1px black;
     border-bottom: none;
}

Makes it a little more "readable" when debugging or making modifications.
the rules would still work if you set it out as;

.class{border:solid 1px black;border-bottom:none;}