Cry moar, bb girl...
Since I've already posted this to every bug report possible and alerted the popular CSS blogs (granted, they probably already know about this even though none of them have posted anything about it! argh...), I figured "Hey, let's cry to rp_tutorials, too."
I'm working on an extensive stylesheet for Bloggish, which I'm tentatively titling "Wackadoo" and you can go play with what I've done with it so far at graphically (it's at least a couple weeks worth of work away from completion, FYI.) I could blather about its features, but I'll save that for when I actually post it for use.
ANYWAY... While working on the styling today, I discovered something that's not so awesome about cross-browser support. Usually, it's Internet Explorer that's the culprit, but today it is Chrome. Yes, Chrome - the fabulous browser in which everything is typically hella cool and gets touted as the answer to all of life's problems, etc. etc. The unfortunate problem I've found with Chrome is that uses the Open Source project Webkit as its CSS engine. Safari also uses Webkit and shows the same downfalls as Chrome. What is the particular downfall that I found? The lack of support for the :first-line selector style definition on elements with content defined in the :before pseudo-element. Boo. This probably means jack squat to most users, but for advanced CSS users, I wanted to point this out because I was splitting hairs over it all afternoon trying to make it work. Basically, for those of you who know what I'm talking about, if I give content to the :before pseudo-element and try to style the first line (e.g. making it look like header text) it doesn't work. Styling of the first letter via the :first-letter selector on the main element does work, but not :first-line. :(
I also found a bug report on Bugzilla that is hundreds of lines long that lists the styling not supported by Webkit, which makes me sigh wearily, but at least my current Bloggish style looks nice in Chrome, unlike Internet Explorer. :|
P.S. Mods - Should there be a tag for CSS/stylesheets since they're different context than HTML?