I came across a bizarre behavior that I figured out how to fix but have no idea what causes it. When I install the module, all of my input fields (without FCKe) stop displaying the cursor. I can still type in and move around (and select) but I don't know where I am the field (a big problem). Also, when selecting parent terms in /admin/content/taxonomy/edit/term, the multioption window does not let me select items on click. I can use the arrow keys to move up and down and space to select but not the mouse.
Well, here's the culprit (line 2 in admin_menu.css):
#admin_menu { position: fixed; top: 0px; left: 0px; font-size: 9px; background-color: #101010; width: 100%; }
I found it by removing bits of the .css file line by line because I couldn't find anything related to the input tag. When I change the font-size to 11px or .85em or up, everything works fine. So that's what I did and I'm happy. However, I am completely mystified as to how this is possible.
There is one unfortunate consequence of this. The Site Configuration menu tends to get pretty long on complex sites and with the larger fonts it extends off screen. And it's not possible to scroll with it. I tried applying some techniques from the Steve Gibson technique of pure CSS menus: http://www.grc.com/menu2/invitro.htm which allows such scrolling but to couldn't figure out which bits were doing what in the sea of CSS hacks. So, the only solution, I know, is to break the menu into submenus.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | admin_menu.css.absolute.patch | 802 bytes | sun |
Comments
Comment #1
yched commentedSimplemenu had a similar issue and fixed it : http://drupal.org/node/108098
(not sure the fix for them applies to the "drupal administration menu", though)
Comment #2
sunIf I go to /node/add/xyz I'm able to reproduce the described behaviour, but only in required fields. The cursor is displayed correctly in any other non-required fields, f.e. in 'Log message' (Fx 2.0.0.1 on Windows XP/2003). Is someone able to confirm this?
If so, we should search for interfering styles on required elements.
Being fix positioned and staying at the top of the window is a major advantage of Drupal Administration Menu. Applying
position: staticwouldn't be better thanposition: absolute, since static is the default positioning for HTML elements. Although applyingposition: absolutewould make the menu also compatible to IE, I'd generally prefer a solution that fixes this cursor bug, but is not based on absolute positioning.Comment #3
sunIf I change the theme to chameleon, marvin or pushbutton I can not reproduce this bug anymore. Can someone confirm this, too?
Regarding Garland and Minnelli themes, we already had to insert additional styles to fix some mystic margins on the left of each menu item in Admin Menu. So I really wouldn't be too surprised if there are some more bugs with those themes...
Comment #4
techczech commentedI had the same problem with my modified version of Chameleon.
Comment #5
sunIt seems there is another CSS-related bug, which causes entries in multiple select fields to be not selectable in Firefox.
So to fix these bugs - shall we change positioning to absolute then?
This would also open the door for IE compatibility.
Comment #6
techczech commentedI vote for absolute, if it makes it IE compatible - I prefer fixed for myself (FF bound) but if I want to extend my pool of admins on a site, I can't rely on them being FF only.
Comment #7
yched commentedDunno if it is related :
Admin menu prevents embedded flash players (for instance the ones added by audio.module) from working.
They just don't get the click, and do not seem to get the hover as well (no pointer change), is if there was something "above" them.
If I scroll the page and have the player in the lower area of the viewport, everything works ok, but there's a "frontier" above which the player won't receive mouse signals (I point that because I noticed this with the disappearing cursor as well)
If I disable Admin menu module, everything is back to normal.
Comment #8
sun@yched: Did you try the patch, i.e. changed from fixed to absolute positioning? If so, are there any effects?
Comment #9
yched commentedEr, I did not actually.
It seems to work :-)
Comment #10
yched commentedBTW, if you go that way (position:absolute), you probably need to replace the margin-top:20px on the body
Of course, it's a shame to lose the 'always on top of the viewport' feature, but if it's the only fix (and I'm not enough of a css guru to come up with something else)
Comment #11
techczech commentedI have it working with the audio module flash player without a problem (but my fix was to increase the font-size which fixed all my problems).
However, on my test site, which has every setting imaginable enabled, the menu gets too big and sometimes leaves trails on the screen when I scroll with the mouse-wheel - even on a freshly opened FF (machine with Core2Duo and 2GB RAM).
Comment #12
sun@bohemicus:
@yched: Seems like we indeed have to wait for Fx 3 and IE 8... But why do we need to remove also margin-top?
Comment #13
techczech commentedI applied the 'absolute' positioning patch and it fixed all the problems including the menu overflow and trailing (no need for a new issue, then, unless you think it's needed). I can now also scroll through long menus.
I did come across a little annoyance, though. Some of my themes have margins applied to the body tag to avoid container divs and the absolute positioning puts the menu inside that. So I had to change the positioning line to:
#admin_menu { position: absolute; top: -25px; left: -3px; font-size: 9px; background-color: #101010; width: 100.6%; }I doubt there's anything that can be done about that, though. Overall, the absolute positioning is the better solution.
Comment #14
sunComment #15
sunCommitted. Thanks for testing!
Comment #16
(not verified) commented