Frame/grid unstable since newest update
-
-
it's live at strindberg.se
It is a problem concerning the mobile menu. I think it appeared since you changed some of the code with the new update. It would be nice -i assume- to switch some of the values to percentage instead of pixels when it comes to the function of the mobile menu.
The problem with the new update is that I can't dictate how the menu should appear next to the logotype and the text below. When opening the menu it appears rather awful at the moment.
-
hey it seems that you need to adapt your custom css to make it look right again.
your phone menu is "position: relative;" so whenever the phone menu is shown, it pushes down all the other content.
I hope I understood the problem correctly.
-
Hi!
It is a desired effect wanting to push down the content rather than layering it on top.
I do not understand how to change the color of the menu when active on a darker background ā e.g. it would be nice if the "index"-page had a white menu instead of gray. This used to work with the current custom css, but that is not the case anymore. It does though work in desktop-mode.
Thanks š
-
Dear @ecoistic
can you post a link to your website?That makes it easier.
You can overwrite the LayTheme CSS when you put !important at the end of the CSS statement:
https://css-tricks.com/when-using-important-is-the-right-choice/Best!
Marius
-
-
Dear @ecoistic
you can use the SLUG to address specific pages. For example:.slug-homeThe pushing down of the content seems to work, right?
And with this you can address the active menu point:
.current-menu-itemSo you can use this as CUSTOM CSS and modify the active menu point.
Best!
Marius
I also code custom websites or custom Lay features.
šæ Email me here: šæ
info@laytheme.com
Before you post:
- When using a WordPress Cache plugin, disable it or clear your cache.
- Update Lay Theme and all Lay Theme Addons
- Disable all Plugins
- Go to Lay Options ā Custom CSS & HTML, click "Turn Off All Custom Code", click "Save Changes"
This often solves issues you might run into
When you post:
- Post a link to where the problem is
- Does the problem happen on Chrome, Firefox, Safari or iPhone or Android?
- If the problem is difficult to explain, post screenshots / link to a video to explain it
