EDIT 2
I am using Chrome's element inspector.
/EDIT 2
EDIT
I've had some success with ul.menu li.leaf a.active-trail, ul.menu li.leaf a, ul.menu li.leaf a:link, ul.menu li.last a:visited, ul.menu li.leaf a:active{ ... } Although the lower level (customizeable) admin bar is still affected, it is readable. I would still prefer to be able to target the sidebar entirely without effecting the admin bar. And why the sidebar links recognize this long string but nota.menu:link is still a mystery to me.
/EDIT
Hi all.
I've stumbled on a problem I can't seem to resolve here. I'm a beginner in Drupal and know a bit about CSS.
I can't seem to style the sidebar links separately from the link on the admin bar (when you're logged into your site). This is a problem because I want to give the links in the sidebar navigation a large button form which makes the admin bar links unreadable.
I've trying playing around with all kinds of CSS classes in the sidebar area such as region, sidebar, region-sidebar-first by inserting those classes into a.CLASS:link, but no luck.
The sidebar completely ignores things like a.sidebar:link , a.sidebar: visited, #block-system-navigation a:link etc.
The only way I can seem to target this links is by a blanket li a.link , etc., which naturally messed up the admin bar.
I this is probably an easy problem for someone a little more familiar with CSS or Drupal, but I'm really stumped.
Any help would be appreciated.
Thanks!
Comments
Comment #1
echoz commentedRather than guess, use a tool like FireBug to see what the classes are effecting what you want to target. I'm not running this version, but I know the sidebar specific classes are not on the anchor tags, they will be above your links, so use descendant selectors (google it), probably .region-sidebar-first for example, then the anchor or list tag below it, separated by a space. This targets those elements only in that sidebar.
Comment #2
dotparfait commentedEDIT: I was trying to solve this problem using both descendant selectors AND Chrome's Element Inspector. Neither of these resolved the issue. I would like to change this from "fixed" back to open. Thank you.
Thanks, I have been. I have been using Chrome's inspector element or otherwise I'd have no idea these classes exist! lol
I'm not sure I understand the details of your response but I will Google them like you suggested. Thanks!
Comment #3
dotparfait commentedComment #3.0
dotparfait commentedMade some progress on my own but problem still persists in some areas.
Comment #4
johnalbinclosing old support issues
Comment #4.0
johnalbinAdded more details to further explain my initial testing procedure.