styles not shown alphabetically?

[hobnail]

Originally Posted by snarkophilus

I prefer to see margin options in top,bottom,left,right order.

That tends to be the order of importance for me as well. If you only need to set the top non-zero, no need to list them all, you could do

{
margin: 0;
margin-top: 1em;
}

I often see style sheets giving all four as zero (margin-top, etc.) and wonder if they know about using just margin to set all four, either one zero or four zeroes.

[theducks]

margin: 1em 0 0 0 ; is a lot less keystrokes than the 2 liner

[Turtle91]

I prefer the shorthand method as well:
margin:1em 0 0 0

It works for me and my reading devices. I have been told that some older models may not support that standard, though. Make sure your target devices use it!

[snarkophilus]

Originally Posted by hobnail

If you only need to set the top non-zero, no need to list them all, you could do

{
margin: 0;
margin-top: 1em;
}

Ah, that does work! I've wondered. I'll use that now .

I often see style sheets giving all four as zero (margin-top, etc.) and wonder if they know about using just margin to set all four, either one zero or four zeroes.

I'm happy to use "margin: X 0 0 0" for specifying a top margin but I always find the order of the last three quite nonintuitive. I notice in your example you've said "top, etc." That's about where my brain gives up too .

[hobnail]

Originally Posted by snarkophilus

Ah, that does work! I've wondered. I'll use that now .

I'm happy to use "margin: X 0 0 0" for specifying a top margin but I always find the order of the last three quite nonintuitive. I notice in your example you've said "top, etc." That's about where my brain gives up too .

You start at the top and go clockwise, but I can't even remember that; sometimes I wonder if you start at the top or left (since we read left to right).

[theducks]

Originally Posted by snarkophilus

I'm happy to use "margin: X 0 0 0" for specifying a top margin but I always find the order of the last three quite nonintuitive. I notice in your example you've said "top, etc." That's about where my brain gives up too .

12, 3, 6, 9
CLOCKWISE

[Turtle91]

Originally Posted by snarkophilus

... but I always find the order of the last three quite nonintuitive...

They had to come up with some standard...most countries understand clock-wise rather than widdershins and there are a significant number that don't read ltr.

...although it is depressing how many kids these days can't read an analog clock!

[DiapDealer]

Just remember to go counter-clockwise when you're below the equator.

[snarkophilus]

Originally Posted by DiapDealer

Just remember to go counter-clockwise when you're below the equator.

Damn you! Just when I thought I'd gained some sort of understanding, you throw this at me!

[GrannyGrump]

Re: using "shorthand" margin css (margin:1em 0 0 0 )

A long time back, there used to be a bug in Nook devices (and maybe others) that messed up margin settings if they were NOT in" LONGHAND".
I have used the "long" css ever since.

Originally Posted by GrannyGrump

(post in 2014) the Nook bug -- it doesn't like margin settings in the "short form". (discussed on this thread: https://www.mobileread.com/forums/sh...d.php?t=223586.)

I'm trying to remind myself to always use the long form, explicitly defining margin-top, margin-left, etc.

Does anyone know if this is still a problem?

[RbnJrg]

Originally Posted by theducks

margin: 1em 0 0 0 ; is a lot less keystrokes than the 2 liner

margin: 1em 0 0; is even shorter

[Turtle91]

Originally Posted by GrannyGrump

Re: using "shorthand" margin css (margin:1em 0 0 0 )

A long time back, there used to be a bug in Nook devices (and maybe others) that messed up margin settings if they were NOT in" LONGHAND".
I have used the "long" css ever since.



Does anyone know if this is still a problem?

What's a Nook?!?!