"Use Browser Hight for Row High" is broken
-
"Use Browser Hight for Row High" is broken on mobile after Update to 2.7.6. It works when I resize my browser window, but should work instantly ;)
Thanks for help.
Go to www.albrechtgaebel.de to see the problem. THX.
-
Dear @albrecht
where exactly on your homepages is this happening?
For me it works. Do you have everything updated?Best!
Marius
-
Hi Marius!
its at the Frontpage. Screenshot attached. If you resize a small Browser Window a bit it works, but if you visit it on your phone you will see the prob. ;)
Updated everything and refreshed the cache... problem is on chrome as on safari...
![alt text]( image url)
-
Dear @albrecht
that is strange. On my test website it works well.
Are you updated?
Did you have a second look into the custom mobile layout?Best!
Marius -
Dear @mariusjopen
I located the problem. It was a new CSS Code which I puted into the Custome CSS "Head Content". The script was the one to jump to specific Pixel on the Page (via #hashtags), which Armin explained in his YT Tutorial. Did you understand me?
Maybe the Script is buggy? The Function "jump to Pixel" is nice and it would be nice to use it later.
This Code:
<script>
jQuery(document).on( 'click', 'a[href*="#"]', function(e){ e.preventDefault(); var hash = jQuery(this).attr('href'); var el = jQuery(hash); var top = el.position().top; jQuery('html, body').animate({ scrollTop: top }, 300, 'swing', function() { window.location.hash = hash; } ); } ); window.laytheme.on('newpageshown', function(){ var hash = window.location.hash; var el = jQuery(hash); var top = el.position().top; window.scroll(0, top); });
</script>
-
Dear @albrecht
do you need the script to run on mobile as well? Maybe we can deactivate it for mobile?Best!
Marius
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