Secondly, I am trying valiantly to either integrate the two tags codes I have, or at least get the multilevel one to work. Evidently I have some really old coding in there and I can't for the life of me figure out how to make this work. Any help would be greatly appreciated. Thanks!
I've finally got this code to work over on my journal but there's just one question I'd like to ask. Is there any way for the sub categories of the tags to be concealed, then revealed when the main category is clicked upon?
You can't really, because LJ doesn't let you have any javascript in your layout, and that's what you really need for that. However, in most recent browsers (but not IE 6) you can use pure css to hide the secondary links and make them pop up when you hover over the top level tag:
// these values can be changed according to your preferences. li.sbaritem ul { left: 90%; width: 90%; top: 0px; background-color: #ffffff; padding: 0; }
Is there any way you could edit this to include group counts, have the tags count to the right, and be in a scrollbox? (Like you did for the one in my current/component layout? I put this code into a Flexible Squares layer I'm customizing and for some reason it's stretching to the right. Just in case you're feeling super helpful and need it, My Layer: #10317219 (there isn't much on it besides your tags sidebar and tags page code).
Comments 4
First off: http://www.livejournal.com/customize/advanced/layerbrowse.bml?id=5311343
Secondly, I am trying valiantly to either integrate the two tags codes I have, or at least get the multilevel one to work. Evidently I have some really old coding in there and I can't for the life of me figure out how to make this work. Any help would be greatly appreciated. Thanks!
Reply
Reply
li.sbaritem {position: relative;}
li.sbaritem ul {display: none; position: absolute; z-index: 5;}
li.sbaritem:hover>ul {display: block;}
// these values can be changed according to your preferences.
li.sbaritem ul {
left: 90%;
width: 90%;
top: 0px;
background-color: #ffffff;
padding: 0;
}
Reply
Reply
Leave a comment