NO BUG: Strange Menu-Submenu-hover problem

When I hover over an item with subitems in the menu, the submenu opens. So far good. If I now move the mouse outside the submenu area, the submenu disappears… of course .

Now comes the strange thing:
When I move the mouse back to the area where the submenu was previously open, it reappears. Especially with long submenus extremely annoying!

I want the submenu to open only when I hover the mouse over the main menu item.

You can see it on this test page:
https://dbi-2.abresch-studio.de/neumarkt/vision/

What am I doing wrong, or how can I solve this problem?
Thanks for any help!

Best regards, kai

Everything looks ok. Is this just a regular nav element? Have you tried disabling plugins to check for conflicts? Which version of Bricks is this?

I“ve made a short video to illustrate the Problem:
https://dbi-2.abresch-studio.de/projekte/abgeschlossene-projekte/am-burgerpark-5/

Thank“s for your reply.
It“s Bricks 1.7.3. and i“ve deactivatet all Plugins testwise. Without a better result.

I“ve noticed, that“s a Problem in Chrome and Edge. Not in Firefox (all actual Browser Versions).

I’m afraid I’m baffled. I’ve tried hiding divs, z-index, and compared your structure to one of my own… they seem identical - but I can’t replicate the issue on one of my sites. Nor can I (with simple devtools tricks) prevent it on your site.
The only thing of note is that the dropdown ā€˜persists’ until you mouse down about 600px, and then it is removed properly. Even if I hide other divs - something think that the menu is 600px high!

If it were me, I would add a second, vanilla nav element somewhere low on the page. Does it have the same issue? Does a drop-down on the nav under the header have the same issue?

If not, add another nav next to the current nav, do they both have the issue?
If not, copy the nav styles, replace the nav, paste the styles.

If all navs have the issue - there must be some script, code or other which is affecting you menus. But this is one for the support team I think.

ok, thank you very much for your effort and help. i will work through your suggestions and report…

Hi Kai,
Thanks so much for your report!

I think the issue is related to your transitions. Currently, you are transitioning all.
Please change the transition property to opacity and visibility and see if it helps.

Best regards,
timmse

Hi timmse,

You got me on the right track. but to change the transition property to opacity and visibility didn’t do it. I have to delete them completely from the custom css and the custom css field of the builder.
Now i don’t have the error anymore. But also no control over the fade in time of my elements. I now think it is a bug after all, because even though I deleted all transition properties, a transition is apparently applied.

Or am I missing something? Is there another setting for default transition duration in bricks?

You can override the transition duration separately in your custom CSS using e.g. transition-duration: 1s;.

So many thanks for your approaches. At least I have a working solution now. I honestly would never have thought of the transition problem.
Have a nice weekend
-kai

Hey Kai,
You’re welcome!