Own up!

[the_eggwhite]

Which of you buggers snuck a ":third-line { }" pseudo-element into the CSS spec, successfully had it implemented in all browsers and then used it somewhere in the vast and arcane CSS I'm working with? Own up! There's no other explanation that I can think of for why a whole bunch of blocks of text on the page I'm playing with suddenly indent by about 1em on the third line.

Sneaky bugger. I'll get you.

EDIT: Fixed!
I don't know why my change fixed the problem - it should have broken it further, but intead it got better. Clearly browsers were confused by my slightly cavalier attitude to rendering blocks as inlines and inlines as blocks, then nesting them each inside the other almost to the point of recursion.

Comments

[blufive.livejournal.com]

If you created a block-inside-inline situation, that's baaaad, and practically guaranteed to freak browsers out somehow (probably in some really crazy way).

[eggwhite.livejournal.com]

It's not quite what I was doing - I was using CSS to tell a block element to render inline, then telling an inline element to pretend to be a block and shoving that inside it - it's quite a common trick that validates and that browsers are happy with.

I was just taking it further and shoving even more inside that... and then more inside that... and so on. I had it working before trying that out, though - I was just trying to make the markup more semantically correct than it had been previously...