SOLVED: Nav Menu Dropdown: Top level background color on hover

I repost this a as bug, because the hover state preview displays it correctly, but when using it the background reverts back to the standard state color, while the text color stays in hovered state.

This appeared on one of my sites at some point and was recently pointed out to me. Thought it was an easy fix (in CSS it is), but I can’t figure this out in Bricks. Somewhere there is a problem. I use CSS properties (variables) [edit: I have also used HEX values, with the same result). I have rebuilt this menu on a local staging site and disabled any custom css (WPCodebox) used previously (latest Bricks version 1.9.x). This still happens:

I use the primary col (blue) as the BG for the menu background and the hover state text color. The orange --accent is the active or selected background.

When I turn on the :hover state preview the parent item shows it supposed to highlight. The normal state shows the menu during design. But in the preview (and in browser) the actual preview is different…
I should add, its the COLOR of the the font that gets applied correctly, but the background-color does not.

Again, and easy fix in CSS, but what am I missing in Bricks?

Hi Sebastian,
Thanks so much for your report!

Where it has been already reported?

Would you be so kind as to provide a short screencast using https://jam.dev showing and explaining what’s happening? Also, please share the template (using hex colors only) as a json file :v:

Best regards,
timmse

Hi Stefan,

Sorry it wasn’t reported as bug but I had it as a generic ‘get feedback post’, since I was thinking I was missing something. I repurposed it to post as bug, is what I meant.

Here is a screencast I made for elsewhere to ask about feedback, but I have gotten some feedback that this seems to occur not only for me. This also ONLY affects the background-color, and is easily fixed in CSS, just was trying to do it the Bricks way.

Hi Sebastian,
Thanks so much for the video!

Now I understand what you mean and have added the problem to the bug tracker. The selector is the wrong one in this case.

Hi guys,

We’ve fixed this issue in Bricks 1.10, now available as a one-click update in your WordPress Dashboard.
You can see the full changelog here: Bricks 1.10 Changelog – Bricks

Please let us know if you are still experiencing issues.

Best regards,
M