hi

admin glitches with admin_menu when admin_menu is enabled.

admin tries to be shown at top, but its a bit eaten by admin_menu by displaying under it.
it would be best to display it after admin_menu, so part of it wouldn't get hidden by admin_menu.

also, i don't really know what admin has to do with Administration Theme.
the same would apply if admin_menu got into the Administration Theme section.
that is BIZARRE.

CommentFileSizeAuthor
#3 play_nice_with_adminmenu.patch758 bytesdnotes

Comments

occupant’s picture

The issue is that both are absolutely positioning themselves at the top of the window. A quick fix is to add this to your theme's (and administration theme if applicable) css

  div#admin-toolbar.vertical,
div#admin-toolbar.ne,
div#admin-toolbar.nw {
    top:20px;
    }
lpalgarvio’s picture

Version: 6.x-2.0 » 6.x-2.x-dev
Component: Code » User interface
Category: bug » feature
Priority: Normal » Minor

suggestion:

instead of relying on detecting if admin_menu class exists or not, check if the module is enabled.

if admin_menu is enabled, then apply compatibility CSS.
else, apply regular CSS

dnotes’s picture

StatusFileSize
new758 bytes

I'd like to see this module allow for admin_menu as a part of its core functionality. The patch attached is a quick fix that makes them work together with three lines of CSS.

This works perfectly as long as you set admin_menu to always show at the top; if not there will be a 21px of white space. Better would be to display admin tools with 21px of extra space inside the main div on body.admin-menu pages, but I couldn't figure out how to do that really quickly; it seems like there would be a few more things required there.

Of course, the best of all would be to make admin module's administration menu items function without clicking; then I would be willing to get rid of admin_menu entirely... ;)

dnotes’s picture

Status: Active » Closed (duplicate)

Okay, please don't use the above patch... I'm embarrassed to have uploaded it at all, when a little more effort gave a much better solution. Also, I'm pretty sure this is a duplicate of another issue : http://drupal.org/node/692234#comment-3743166