Things that suck about coding CSS

Get Started. It's Free
or sign up with your email address
Rocket clouds
Things that suck about coding CSS by Mind Map: Things that suck about coding CSS

1. Floats

1.1. Clearing floats

1.2. Aligning floats

1.3. why do I even need a float for this?

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

2. Errors

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

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

2.3. 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.

2.4. New node

3. Every browser is a special snowflake

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

3.2. Firefox

3.2.1. Don't look all innocent, Firefox.

3.2.2. The opacity tomfoolery, for one

3.3. Internet Explorer

3.3.1. Because only geeks and developers actually use Firefox.

3.3.2. Heights, they're just b0rked

3.3.3. The box model. Enough said.

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

3.4. Opera

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

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

4. Alignment

4.1. Power! Complete power!

4.2. 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

4.3. Drunk! with.. power!

5. Why does this need a workaround?

5.1. Equal height columns

5.2. New node