SOLVED: Dropdown is accessible when closed

Hey guys,

could someone explain to me why switching between two megamenu points causes this problem? If you switch quickly between the menu items, it is not displayed correctly. Only when you wait a certain amount of time is it displayed correctly.

Have also tried to change transition-duration: unset but problem is the same.

Does anyone have any idea what to do about this?

Thank you very much.

Hi!
Try replacing the classes with these updated ones to see if it fixes your issue (replied to your post on FB too).

a.brxe-text-basic.text--bold, .brx-dropdown-content a.brxe-text-basic.bt-menu-card-ticket__heading.clickable-parent {transition: unset !important;}

Thanks a lot :wink: As in facebook, unfortunately not :confused:

@timmse do you have an idea?

Same problem in my cases. It’s very annoying, and can’t find a solution.
It’s sad it’s been a several Months when the problem reported, but still no solution for it.

@timmse update would be nice …

Hi Manuel,
Sorry for the very late response!

We have also received reports on the problem by e-mail and are working on a solution.

Best regards,
timmse

1 Like

Thanks a lot for your answer.

Hey @timmse ,

Slowly but surely, a solution is really needed. Unfortunately, the problem still exists.
Please let me know how long it will take.

Thank you very much.

@timmse still waiting for an answer.
Thanks a lot.

Hi Manuel,
We apologize for the delay in implementing this fix/improvement. We understand its importance to some of our users, and it remains on our to-do list. Rest assured, we aim to provide an update as soon as possible. Thank you for your patience and understanding.

Thank you very much for your answer.
I would just need an estimate of when this will be implemented as several customers unfortunately already have this “problem” and they want an answer.

Thank you very much.

I would appreciate it if I could tell you specifically when the problem will be solved. But, unfortunately, I can’t.

Hi guys,
We’ve finally fixed this issue in Bricks 1.9.9, now available as a one-click update in your WordPress Dashboard.

Changelog: Bricks 1.9.9 Changelog – Bricks

Please let us know if you are still experiencing issues.

Best regards,
timmse

So cool, thank you very much for the message.