Ticket #6773 (new defect)

Opened 7 months ago

Last modified 6 months ago

Menu: add timeout so submenu doesn't close if mouse touches parent node's sibling

Reported by: smith@… Owned by:
Priority: low Milestone: 2.0
Component: Dijit Version: 1.1.0
Severity: normal Keywords:
Cc:

Description (last modified by bill) (diff)

Add fudge factor for popup. If you click a popupmenu(submenu) and then diagonally slide your mouse, there should be a small timeout to allow you to get into the submenu without it disappearing. If you try the "history" menu in firefox, hover over "recently closed tabs" and sort of go down and to the right to get into the large list. It hangs out for a second, allowing you to get in there. Dojo menus go down unless you keep your mouse entirely in the parent menu item the whole time. This makes for a squirrely menu.

Change History

Changed 7 months ago by guest

I just found another bug, click the little graphic (>) in a popupmenu item you will get an error

popup has no properties http://localhost/gq_smith/apache/web/GQ/js/dojo-1.1.1/dojo/dojo.js Line 322

Changed 7 months ago by bill

  • cc smith@… removed
  • reporter changed from guest to smith@genomequest.com
  • milestone set to 1.4

I agree with (1), but that occurs because we don't have a MenuBar widget yet, see #4634 (so you've basically duplicated that ticket).

I guess (2) makes sense. Whether it should be a timer or react based on distance is debatable; I guess either is OK and the timer is probably easier.

I split off the other bug you found as #6778.

Changed 6 months ago by bill

  • priority changed from high to low
  • summary changed from Menu and Toolbar Behaviors not Standard to Menu: add timeout so submenu doesn't close if mouse touches parent node's sibling
  • description modified (diff)
  • milestone changed from 1.4 to 2.0

Updating title and comment to remove the comment about !Toolbar vs. Menu since that's what #4634 is about.

Changed 6 months ago by guest

bill I would like to suggest that this isn't as low as you think - menus have an expected behavior, and the dijit menus are squirrely and hard to use. I have seen many demos of our software where people struggle with the precision needed to operate it. Certain things just have to be right, basic, core things.

Changed 6 months ago by alex

I'm inclined to agree that this isn't low priority.

Note: See TracTickets for help on using tickets.