NO BUG: Undesired .brx-submenu-overflow-right

Browser: Chrome 130.0.6723.117
OS: Windows 10
URL: https://staging.forestretreats.co.uk/ (Header) pw: carrot
Video: Dropbox

Note - I’ve shown the live site in the video but have reverted it to the previous header whilst this is investigated. See staging site for issue.

As shown in the video - the nav nestable has 2 dropdowns, one is fine but the other has an undesired class applied - .brx-submenu-overflow-right

I can’t see where or why this class is applied, especially as its only applied to one of the two dropdowns.

Thanks in advance for your help!

pw for site is: carrot

Hi Macky,
Thanks so much for your report!

The staging site is password protec… ah, you just added the password :smiley: Thanks!

However, I can’t see the problem in the staging site, no matter how wide or narrow I make the viewport :thinking:

Typically, the class prevents the dropdown content (especially with nested dropdowns) from overflowing if there is insufficient space to the right. In this case, the dropdown moves to the left.

1 Like

Hehe yep saw you typing as I added the pw!

Thanks for your response, however the addition of this class is undesirable. Although you can’t see it it is clearly happening (see video). Can you let me know how to disable the class? If that’s not an option in the builder can you add it as a feature request? Ideally I want full control over classes for any site that I build with Bricks.

Cheers!

It happens at viewport width 2262px and above for me

Aaah, I didn’t make the viewport that wide :smiley:

The problem is that your left value is overwritten. You can’t avoid using !important in this case:

1 Like

Thanks the addition of !important to my class left style has removed the undesired effect of the .brx-submenu-overflow-right class.

So it seems that the .brx-submenu-overflow-right class isn’t working as it should, as there isn’t insufficient space to the right, either above or below the viewport width at which the class is being applied? Is this a bug?

As far as I can see, it works exactly as it should.

Indeed, changing the position of the content in certain situations can lead to unexpected results, which require a custom solution to adapt to the scenario. But I don’t see a solution that works for all conceivable scenarios, as we can’t know where you use which settings to achieve result x or y.

Apart from that, as far as I know we don’t have another report on this - so it seems to work for most users.

1 Like

OK thanks, makes sense. I’ve created a feature request to disable hidden auto-classes like this as it would be nice to have full control of a site.

Cheers!

The helper class is not there to restrict you in anything, but as already mentioned to prevent problems. However, Bricks allow you to create custom elements or use custom code where you are 100% “in control”.

1 Like

Ah yes I could code a custom element. In fact why don’t I custom code the entire site? We use frameworks because we don’t want or need to reinvent the wheel every time we build a website.

I appreciate that your helper classes are there to help, but as clearly outlined in this case it wasn’t helping, and I’m simply asking for the option to turn off