The Issue

So you’ve got two elements sitting atop each other, each with vertical margins. You would expect the margins to add together:

.thing {
 display: block;
 width: 100%;
 height: 200px;
}
.thing-upper {
 margin-bottom: 50px;
}
.thing-lower {
 margin-top: 30px;
}

… so the space between them is expected to be 50 + 30 = 80 pixels. Except they’re not.

When two vertical margins meet, they usually collapse; i.e., in most cases, where the margins of two elements meet, only the larger value is preserved (or if equal, only a single value).

This is the normal flow of the box model, and there are specific cases governing this collapse (blocks with margins but no content, adjacent siblings, etc.).

Solution

Maddening before one knows what's going on, but it’s workable.

The simplest method is to stick with either top or bottom. I prefer margin-bottom, because I usually want to be consistent with how much room there is underneath something. I also often have to override a margin-top anyway (header tags, i’m looking at you).

Other Notes

• There is a -webkit-margin-after-collapse property which can be set to "separate", but of course non-Webkit browsers get no love.

• You can include an :after pseudo-element with display:table, but I like reserving my befores and afters for interesting things.

• Floats do not collapse vertical margins, but you must control width and clearance (width: 100%, clear: both).

• Negative margins are funny. If both margins are negative (who does this?), then they act as if positive, preserving the larger absolute value. If one margin is negative, the negative margin is subtracted from the positive.

• First and last child elements tend to have their vertical margins overridden by their parent, or even extend their margin outside the parent. You can muck about with the properties of the child (like its padding), which sort of "wakes it up" and allows the margins to be preserved. See MDN web docs for painstaking but succinct details.

This tutorial is for mac users.

Burn Image

Insert an SD card into your computer, then open a terminal window and type:

diskutil list

You will get a list of drives. In the example below I have 3 disks, disk0, disk1 and disk2. The first disk is my hard drive and I need to be extra carefull not to accidentally overwrite it with my image. disk2 is my 8GB SD card. Two clues are (internal, physical) and *7.9 GB. See below:

I need to unmount this disk:

diskutil unmountDisk /dev/disk2

Here is an example:

Next I will use the dd command to burn my image onto the SD card:

sudo dd if=~/Desktop/some-image.img of=/dev/rdisk2 bs=5m

You can see I am using the device “rdisk2”. This is much faster than using “disk2”. I found this from a superuser.com question “Why is “/dev/rdisk” about 20 times faster than “/dev/disk” in Mac OS X”

This process will still take a good 10-20 minuts to burn an 8GB sd card. You can type “control-t” at any time to see the progress:

You should get from 4000000 to 10000000 bytes/sec (4 to 10 megabytes per second). If you get less than this you may have a bad SD card.

Once the process has finished you can insert the card into your Raspberry Pi.

Clone Image

Insert an SD card into your computer, then open a terminal window and type:

diskutil list

Again, you will use the dd command with the arguments “if” (in from file) and “of” (output to file) in reverse order from the burning example above.

sudo dd if=/dev/rdisk2 of=~/Desktop/some-image.img bs=5m

Resources

• Download Raspbian: “Raspbian is the Foundation’s official supported operating system.”