March 25, 2005

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

This for Google’s sake, mostly.

But for future ref­er­ence, IE/Mac doesn’t handle ele­ments that have two class names.

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

Because the pro­duc­ers at work are usu­ally making minor tweaks and changes to the lay­outs of the few CSS pages we have, I adopted this tech­nique. In a total bas­tardiza­tion of the OOP term, I think of them as mix-​ins.

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

Anyway, I second any motions to drop sup­port for IE/Mac. Mac users should be smart enough to be using the better options they have.

Filed under: Technology,Web design

Next:
Previous:

Related

  • http://sidesh0w.com/ Ethan

    For what it’s worth, I’ve never had any issues with mul­ti­ple class names on an ele­ment in IE5/Mac; that browser even sup­ports a multi-​class selec­tor (say, “.lede.breaking {…}”), which puts it head-​and-​shoulders above its PC cousin.

    Which is saying a whole lot, I know. :)

  • Chris

    Ethan, (and Google),

    I’m guess­ing the trou­bles I’ve found with mul­ti­ple class names is some­thing along the lines of the this white­space pars­ing bug.