If i add on css:
.mob-menu-header-holder
{
position: static (or absolute);
}
it’s ok but the icon don’t scroll anymore with the page 🙁
____ UPDATE:
Finally, even if the icon is well positioned, an empty column of the page is generated to the right of the main body :/
-
This reply was modified 4 years, 5 months ago by
xmarians.
Hi @xmarians,
I’m not able to reproduce that using Google Chrome.
Can you clear the browser cache and check if that is still happening?
Thanks
I have not yet understood why but I realized that the horizontal scroll that appeared is not linked to the mobile menu plugin and appears only in Chrome.
Already tried to delete the cache but nothing … even in the html code (the same as before) there is no reference to why the body is larger than the assigned size. It’s a mistery
@xmarians but I tested on chrome in a Mac and still can’t replicate it.
With great difficulty and hard work I solved the problem of positioning some elements inside the body of the page!
It was not a mobile menu problem.
Last question: can I restore the sticky style of the menu icon?
That’s great. What do you exactly mean with the last question?
Thanks
Scroll the icon of the mobile menu with the page, when users scroll down
@xmarians
Hi, how did you solve Chrome issue?
I have the same problem with Mobile Menu positioned outside body, with Meris Pro theme.
Thank’s
@memwebproject
Hi! For me the issue was due to the div of the widget of the theme, although it was positioned well on the page, in reality the code created a bigger div and therefore the mobile menu was rightly positioned in the maximum right end available, but leaving the margin of the main body.
By changing the div’s hierarchy and changing some properties of the css, I managed to make the div of the widget coincide with the body of the page and bring automatically the icon of the mobile menu back to its rightful place
@takanakui
Hi! The option was already active, I tried to deactivate, reactivate and delete the cache but nothing has changed.
@takanakui
Eureka! I solved by fixing a value in the custom css, thanks for the support!
