dw_docs | (no subject)

A question about some of the coding--I noticed, when browsing the site, that the navigation strip is still being called as table#lj_controlstrip and all users/comms are still span.ljuser. Is there any particular reason for this? After all, tags such as <lj-cut> have been stripped of their lj-specific nomenclature and the navigation strip isn't a control strip anyhow...

I'd never have noticed but for the fact that I have some very !important CSS declarations in my userstylesheets that are directed at #lj_controlstrip (along with some even more destructive userjavascripts that reorder the selects to my liking) and imagine my surprise when I noticed poor Dreamwidth's nav strip being restyled! *laughs* Of course I can simply reapply my rules to be domain-specific, but I'm curious all the same.

Forgive me if this wasn't the right place for it, but it seemed a bit too impersonal/unnecessary to write to support and I figured that it was much along the same lines as this post, so, hm.

Thanks for all the hard work, everyone! Pats on the back, all around! I'm off to play around with Core2 (which, for someone who occasionally dreams in CSS, is quite exciting).

EDIT: Oh, by the way, been meaning to mention that the semicolon is missing from the end of the last — (—) on this FAQ page.

Flat | Top-Level Comments Only

The other stuff is out of my league, but I've added the missing semi-colon. Thank you for the headsup!

~Carys

No problem! :3

I'm kind of glad that lj-cut still works -- unless [cut] would automagically turn into lj-cut when cross-posting to LJ?

Sadly, I think not. :/

Sorry it's taken me a bit of time to get to this. It's not really a docs issues, but I'm happy to answer anyway. Short version of this is that things like this aren't a priority for us to fix. There are too many references to LJ in the code for getting rid of them all to be a productive use of our time. We want to get rid of anything "LJ" that's directly user-facing, but for things like this that are only going to be encountered by tech-savvy people poking at CSS, it's not a priority.