WIP: The mobile navigation appears briefly in the normal view when the page loads

Bugs
1

Bricks Version: 1.4
Browser: Chrome and Firefox, the newest
OS: macOS

Hello in the forum
Since the update to 1.4, the mobile navigation is sometimes visible for a brief moment when loading a page in Chrome and Edge. It becomes clearly visible with active developer tools.
I have the behavior with websites that I have updated to 1.4 and with a newly created test page with 1.4. without additional plugins.
Attached is a video, the mobile navigation has a red background to make it clear. It doesn’t matter at which breakpoint… The behavior only occurs to me in Chrome and Edge, not in Firefox and Safari.

mobile-menu

2

Hi Heiko,
Thanks so much for your report!

That issue is a strange one, because I’m able to reproduce it on some sites, but not on others.
We will take a closer look soon.

Best regards,
timmse

3

Thanks for the information.

Transitionally I help myself with the following code, because it does not show up.

.bricks-mobile-menu-wrapper {
display: none !important;
}
@media (max-width: 991px) {
.bricks-mobile-menu-wrapper {
display: flex !important;
}
}

2 Likes
4

All items with “display none” appear briefly, e.g. skip navigation, sub-menus of the navigation, etc

5

Issue reappeared from 1.7.1
In 1.7 it was fixed (maybe also in 1.6.2 not sure)

6

Yep, It’s a neverending story :smiley:

7

Hey @Deadlift79 , can you please send temporary login data and a link to this thread to help@bricksbuilder.io so we can take a look at the settings in detail?

8

Just sent. Have a fine day!

9
  • Solved*

I’ve had the same issue with the new menu builder and offcanvas for mobile.
Digging deeper I’ve found that, in my case, is related to perfmatters “disable emojis”. (Same if I disable with Bricks).
Unchecking it fix that behavior.

10

Hey guys,
Quick update on our investigation:

In general, the problem only seems to occur under the following circumstances:

  • Chrome + open dev tools.

With closed dev tools nothing flashes at all in our tests. We honestly haven’t found a specific reason for this yet, but don’t see it as a real problem either.