What version of bp are you using? I thought this was fixed in the trunk. Try updating to svn trunk.
It’s not fixed in trunk either it seems. It’s back. Happening here also. I’ll put in a trac ticket.
From the trac ticket comes a fix for the masses…
In admin-bar.css, at line 55, under…
#wp-admin-bar ul { /* all lists */
REMOVE…
height: 30px !important;
ALTERNATIVELY REPLACE WITH… (might be needed to keep ie6 happy?)
height: auto !important;
The problem with setting the UL height to a set amout is obvious once you see it… Moving the mouse beyond the 30px point confuses the CSS, because the LI’s an A’s are outside the bounding area of the UL. Move the mouse 31px down, and the suckerfish JS fights the CSS to eventually say “remove sfhover” and the menu disappears.
if you’ve bpdev plugins installed you can do that without touching the code:
<?php
function register_my_css() {
bpdev_theme_register_style(
‘my-css-hack’,
‘My Css hack’,
‘my_css’,
‘on’,
‘on’
);
}
function my_css() {
?>
#wp-admin-bar ul {
height: auto !important;
}
<?php
}
?>
and save it in a new file under /mu-plugins
So when bp will update that, you can switch this thing off via the WP Admin-> BPDEV Admin -> BPDEV Theme
Thanks for the fix to this bug John!
Just add to site-wide.css for now, skip the plugin 
@Nicola:
Doesn’t work – just kills all styles. BTW: I’m not using your theme. So this is the problem Your hack only with your theme.
CSS hardcoding – great.
guys where is this file? I’m not familiar with buddypress yet
ty
Brian, the file itself is in bp-core/css/admin-bar.css, but like Jeffca mentioned you can also make a site-wide.css file, and place it in your currently active home theme\’s /css directory, and it will work everywhere within your site, even inside the member theme.
That way you\’re only editing one file, and it\’s on your own terms.
I’ve added my fix to a trac ticket so it will get reviewed and possibly fixed in the core for future updates. The goal with all of this is NOT to edit or hack the core, but to have the core be as universally compliant as possible, and still allow for customization later.
so the fix I’m about to do is only for what then?
For fun? 
It’s a fix that you’re going to want to keep in the back of your mind, knowing that it will probably become part of the core and something you will never have to think about again.
I sis the css and it’s working perfect
Thanks guys!
