Various questions for Librarian's Dream + Mobility

[sheliak]

My current layout is Librarian's Dream, and I've been playing with Mobility on my test journal. I've run across a couple things in both that I can't figure out how to wrangle.

Librarian's Dream

1. Multilevel tags: I've noticed that some multilevel tags display oddly. Basically, when there's an x:y:z tag, what's displayed is x:y, and then z as if it had been tagged x:z rather than x:y:z. Does anyone know how to fix this and add an extra indent to third-level tags?

2. The profile icon has a bit of padding underneath it. I'd like to either remove that padding, or add equivalent padding above + to the left, so that the icon appears more centered. Is either of those possible?


Mobility

This is less urgent, I've just been poking at the style and trying to figure out what I can and can't do.

3. Is it possible to make the border disappear on the next/previous button, and the [flat/top level comments only] bar on entries? (Or, for that matter, to get rid of all borders on everything?) I've been able to figure how to turn most borders on and off, but those have eluded me.

4. Is it possible to set a background image for comments, next/previous, archive, tags page, etc, as it is for the entries/modules/header? (I'm trying to use a (hopefully unobtrusive) textured image instead of a solid color, basically.)

5. If the latter is not possible: is it possible to change link & text color only on the next/previous?

(Current Mobility attempts at beta_lyrae.


Thanks in advance!

Comments

[momijizukamori]

I'm about to go out of town for the weekend, but if you don't have answers by Monday, please poke me to have a look :)

[sheliak]

Thank you for your kind offer!

[momijizukamori]

Not a problem - did you get everything sorted, or did you still need help?

[sheliak]

Most of it is sorted!

I didn't get an answer for stripping the padding away from a profile icon in Librarian's Dream, but I did get a way to add padding in other directions. I'm still curious about the first one, but I've got a solution that works for my actual journal.

And the multilevel tags thing is still unsolved. fueschgast thinks that the problem isn't a CSS issue, so I'm not sure if there's anything to be done about it.

(I've also got a new batch of questions regarding a new Mobility attempt, but maybe I should make a new post for that one...)

[fueschgast]

1. Is that problem solved by now? On entries the tags look complete and on the tags page the 3rd level is indented.


2. .userprofile-userinfo .userpic {
display: table-cell;
padding: 4px 0px 0px 8px;
}

.userprofile-userinfo .journal-name {
display: table-cell;
vertical-align: middle;
}


3. For the specific ones:
   .topnav, .bottomnav, .comment-pages {
border: none;
}
   
   For all:
   div {
border: none!important;
}
   In that case, if you do want a border on a specific div, you need to add !important to that line.


4. I don't know if I understood you correctly, but if you want to change the background of the specific pages, here's how you address them:
   body.page-recent
   body.page-entry
   body.page-reply
   body.page-archive
   body.page-month
   body.page-day
   body.page-read
   body.page-network
   body.page-tags


5. As I can't see any next or previous, this is only a guess:
   .topnav a, .bottomnav a {
color: #ff00ff;
}

[sheliak]

Thank you so much!

1. It's not--the problem is with the tags module (on recent entries view and so on). I've got a three-level tag that's blending in with the two-level ones right now--my tag is "fandom: naruto: dreaming of sunshine", and it's showing up as if "fandom: dreaming of sunshine" followed "fandom: naruto". So it basically looks fine until you notice it's not in alphabetical order. (I know it used to look weirder, at least on preview--for a while I remember seing third-level tags wrapping around and looking like first-level ones.)

2. Thank you, that helps a lot!

3. Thank you! Most of that works for me--although when I try the first version, for some reason the comment borders stick around even though the topnav/bottomnav ones disappear. Not sure what's going on there.

4. I'm not trying to change the page background. On the test journal, I've got journal entries and modules showing up with a slight pattern instead of being a solid color--I'd like to get the same effect with the parts of the layout that are currently solid colors. For example, I'm trying to get the light woodgrain pattern to show on the topnav (thanks for helping with that!). Or here, the entry itself has the background picture I'm trying for, but the comments have a flat-colored background. Does that make any more sense? I know I don't have a very good vocabulary for this stuff yet.

5. Ah, sorry! I forgot that so much of that journal was private. (I set entries per page to 5, so the next/previous ought to be showing up now.) But yes, that seems to work, thank you! (I think the problem was that I couldn't figure out that topnav and bottomnav were the names I needed--I kept getting lost on the documentation wiki.)

[fueschgast]

1. That doesn't sound like a CSS problem, so I can't help you with it.

3. Maybe the .comment-pages border gets overridden. You could try adding !important.

4. Oh! Okay, those classes will take a bit of work to collect and I don't have the time right now. You could do it yourself though. Did you know that you can right-click on a page (but not on a link or an image, unless it's a background picture) and view the source code? To make it easier to find a class, you can search for what's in the div you're looking for. So in the case of the comments, you can search for a part of a comment's date (not the whole line, because "Date:" and the date are divided by html tags) and find that the class is .comment.

[sheliak]

1. Good to know!

3. Turned out to be a class mismatch again--I tried .comment instead of .comment-page and that did what I wanted.

4. Thank you! I managed to track down all of them. (And it turned out that I was using the wrong syntax to set the images, too, but I managed to figure out what I was doing wrong there by page-inspecting from a style that did it successfully.)

Thank you!