Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

Things that suck about coding CSS by Mind Map: Things that suck about coding CSS
0.0 stars - 0 reviews range from 0 to 5

Things that suck about coding CSS


Clearing floats

Aligning floats

why do I even need a float for this?

wait, you mean a float in this element actually modifies an adjacant element? what?


Is it the margins? Is it positioning? Is it actually the other element? Did you remember to hit 'save'?

Spending an hour tearing your hair out only to discover you forgot a closing brace halfway through the stylesheet.

If you have to ask for help, make sure you have EVERYTHING standards-compliant first, or the people in #css will be big ole meanies.

New node

Every browser is a special snowflake

Don't forget to test in IE6, IE7, FF2, FF3, Safari, in XP, MacOS, and Linux...look, a monkey


Don't look all innocent, Firefox.

The opacity tomfoolery, for one

Internet Explorer

Because only geeks and developers actually use Firefox.

Heights, they're just b0rked

The box model. Enough said.

Thank god for the underscore hack...I mean, the asterik hack...I really wish they wouldn't bother fixing these bugs...


It's fully compliant! Isn't that exciting! Nobody uses it though!

Except Wii and mobile browsers, which means you have to test for it anyway!


Power! Complete power!

And complete power is useless if you don't completely grasp inline elements, block elements, z-indexes, positioning floats, and a great recipe for a martini

Drunk! with.. power!

Why does this need a workaround?

Equal height columns

New node