I have a header template with a logo and a navigation menu that has a submenu (standard Wordpress menu).
In the header template I have activated Fixed Header and push-up after 200px and a scroll-shadow.
In the Chrome browser on Windows, when I scroll up, as soon as the 200px are reached, the header shifts suddenly left (I guess around 20px?) and then it disappears. On the right side of the header for a split second a scrollbar is shown, which I guess is the reason why the header shifts left.
When I use the exact same header with a navigation menu that has NO submenu, then the header works fine and no shifting to the left happens when I scroll up.
So I guess something goes wrong with the header hiding / scrolling-up functionality if the navigation menu has a submenu.
I noticed the same for mine. Can we expect a fix in the builder instead of adding multiple custom codes for the fixes(not supposed to be done by the users) to our site? Otherwise, we must remember all the custom codes for it every time we build new sites.
Hi Jornes,
Of course, you can expect a fix (see the title, it’s in progress). Using the custom CSS allows you to fix the issue immediately, but no one forces you to add it
Thankful that this issue is resolved in version 1.7. I was confused a lot and now there is a solution. Thank you Bricks team, I appreciate what you guys are doing
I’m making a onepgae size, and maked my “header” to fixed.
But in mobile view the section is overflow. You said, in bricks 1.7 beta was fixed, but no.
If I turned off the fixed css with chrome devtools the overflow problem is gone, but my header is not “sticky”.
Hi,
This report was about a vertical scrollbar, not an overflow I don’t see a scrollbar on your screenshots though. Nevertheless, a link would be very helpful.
The problem was really the 3 code elements. I put it owerflow hidden, and its working.
I suspected the header because only that one element owerflowed from the picture, the code elements were visually perfectly fine.
Thank you for the positive feedback about the layout.
It is far from ready, and it takes a disproportionate amount of time, compared to the fact that it will “only” perform the function of a landing page.