IE/Mac doesn’t handle elements with two class names

This for [Google’s sake](, mostly.

But for future reference, IE/Mac doesn’t handle elements that have two class names.

And this sucks, because it’s a common technique I use to make my CSS a little more user adaptable.

Because the producers [at work]( are usually making minor tweaks and changes to the layouts of the few CSS pages we have, I adopted this technique. In a total bastardization of the OOP term, I think of them as mix-ins.

Say, you’ve got an <h1> with a class=”lede”, but the producers need to make it bigger and red when it’s a breaking story. Except for IE/Mac, they could do something like this: class=”lede breaking.”

Anyway, I second any motions to [drop support for IE/Mac]( Mac users should be smart enough to be using the [better]( [options]( [they have](

About Chris

Python developer, Agile practitioner trying desperately not to be a pointy haired boss.
This entry was posted in Technology, Web design. Bookmark the permalink.

2 Responses to IE/Mac doesn’t handle elements with two class names

  1. Ethan says:

    For what it’s worth, I’ve never had any issues with multiple class names on an element in IE5/Mac; that browser even supports a multi-class selector (say, “.lede.breaking {…}”), which puts it head-and-shoulders above its PC cousin.

    Which is saying a whole lot, I know. 🙂

  2. Chris says:

    Ethan, (and Google),

    I’m guessing the troubles I’ve found with multiple class names is something along the lines of the [this whitespace parsing bug](

Comments are closed.