something causes menus to require 2 clicks
| Project: | DHTML Menu |
| Version: | 6.x-3.4 |
| Component: | User Interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
During the course of using my site, inevitably something happens that cause the DHTML menus to require two clicks in order to expand or collapse them. Leaf nodes still only require one click to display the related page, but parent nodes seem to ignore the first click. It feels almost as if the first click simply gives the item focus and doesn't actually execute any of the javascript, then the second click causes the action to happen.
When this situation occurs, the required two-click behavior is the same for all menu items (rather than just one node or branch) and tends to remain that way through several page displays. Eventually, the one-click behavior comes back, but then after enough time the two-click behavior resurfaces. I know that I will see the behavior as long as I navigate around the site for more than 5-10 minutes, but I can reproduce the situation with absolutely certainty with a specific sequence of events.
I use Firefox (2.2 and 3.0) on Windows XP a majority of the time, and at the moment I can't recall if I've seen this behavior with IE or not.
I wish I had more detail to offer you, and I realize it's unlikely you can do anything without a readily reproducible case, but I'm hoping someone might have seen this in the past and be able to offer a quick solution or workaround. Thanks.
#1
I can now offer another detail on this. I just noticed that the icon displayed to the left of the menu initially defaults to the one which would normally be present if the menu item was expanded, even though it is not expanded and no child items are displayed. The first click which I previously believed to do nothing is apparently actually calling the code to collapse the node, which visually does nothing except change the icon to the not-expanded icon. The second click then expands the node properly, showing all the children.
So my question now is, what causes a node to think it is expanded, yet not display any children?
Thanks.
#2
I've had this problem for a while myself while testing, but was pretty sure it no longer occurred. Could you try the 3.0 beta to see if it still happens there?
#3
6.x-3.0-beta seems to work just fine! Thanks.
For what it's worth, 6.x-3.0 doesn't seem to work at all with the Devel Theme Developer module. I don't think it is anything worth investigating, and certainly not fixing, but might be worth a release note to prevent someone else from reporting a bug only to find out it's caused by Devel Theme Developer.
Thanks!
#4
I've tested a bit with 6.x-2.2, but haven't been able to reproduce it.
I'll keep this issue around in case it does happen again.
#5
Hi,
I can reproduce this case with 6.x-3.4, even on the test page
Use these settings:
Now, to trigger it go to the test page and:
Regards,
Antonio
#6
Changing category and Status.
Any comment about this one?
Maybe you can simply remove the choice to Close menus when their parent menu is closed doing this by default, this would prevent the bug from happening, and looks like a sane behaviour anyway.
Regards,
Antonio
#7
Hi,
With 6.x-3.5, I get beautifully smooth menues that expand quite nicely. However, if I have a menu item "tech-toc" with sub-items "tech-1", "tech-2" etc., I can't reach the contents of node "tech-toc" (which is associated with the menu entry "tech-doc", when clicking on "tech-toc", the menu expands, but the node is not displayed. Clicking on the sub-items "tech-1", "tech-2", etc. works well.
The only way to solve this is to configure the module at ./admin/settings/dhtml_menu to display an additional menu item to open the page ("Unter jedem ausklappbaren Menüpunkt einen Extralink einblenden, der die Seite öffnet."). This gives me a menu structure like so:
tech-toctech-toc
tech-1
tech-2
My users were irritated by this double menu entry and complained about this "bug". So IMHO the node should directly open when the menu item is clicked on. So simply what I want is:
tech-toctech-1
tech-2
Since I'm not sure how the module is supposed to behave, this might be an related issue to the issue above ("something causes menus to require 2 clicks", or the same issue, or a bug report, or a feature request.
Thanks & greetings, -asb