Something (presumably either CSS or Javascript) is causing the admin menu to not collapse itself upon mouse-out.

This is easily reproducible:

  • Mouse-over a menu item to trigger the drop-down
  • While menu item is open, move mouse up and off the browser window
  • Return the mouse to the browser window outside of the menu area
    • Expected: the menu eventually collapses; pressing "esc" or clicking outside the menu causes it to close.
    • Actual: the menu stays open indefinitely, regardless of other mouse or keyboard interactions with the page.

or

  • Mouse-over a menu item to trigger the drop-down
  • While menu item is open, use ctrl-tab to change browser tabs
  • Return to the original tab
    • Expected: the menu eventually collapses; pressing "esc" or clicking outside the menu causes it to close.
    • Actual: the menu stays open indefinitely, regardless of other mouse or keyboard interactions with the page.

This leads to a few UI bugs:

  • Menus appear to be "stuck" open
  • Stuck menus interfere with other page interactions by overlapping page content.
  • Multiple menus can be open at once (see attached screenshot)

Suggested resolutions (any or all would):

  • Poll the browser for mouse position. Close the menu after X time if the mouse is not hovering.
  • Close the menu on "esc" keypress.
  • Close the menu on mouse or keyboard interaction on any other part of the page.

Tested in Bartik (core), as well as custom adminimal- and omega-based themes.
admin_menu 7.x-3.x-dev
Firefox 35.0.1
OSX 10.10

CommentFileSizeAuthor
double-menu-all-the-way.png75.72 KBAaronBauman
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

truls1502’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: +postponed2w

I am sorry for no reply until now.

There are many issues regarding this module admin_menu which is a bit difficult for us to follow up since some of the issues might be already outdated, or is already fixed by the module or any other modules or itself core which means that the problem might no longer need to be fixed.

We can see that the issue has been created for a few years ago, I hope it is okay for you that I am postponing the issue, and give you around two weeks. If you still face the problem, could you tell us the step by step when until you get the error message or what is frustrated you, and a list of modules you are using related to admin_menu and a screenshot that might help us? So it makes us easier to reproduce your issue.

However, after two weeks with no feedback - we will close this issue. So in case, you noticed it after the issue is closed, do not hesitate to reopen it like and fill information which is mentioned above.

So before giving us a feedback, do you mind to test it again with our latest 7.x-3.x-dev?

Thank you for understanding! :)

truls1502’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
Issue tags: -postponed2w

This issue has been automatically marked as closed because it has not had recent activity after the last post.

However, if you or someone is still facing the same issue as described to the issue, could you please to re-open the issue by changing the status of the issue, and add an explanation with more details which can help us to reproduce your situation.

Again, thank you for your contributions! :)