• Resolved jazzminus

    (@jazzminus)


    Hi there,

    thanks for your awesome plugin. I just wanted to let you know that I am observing an error when I enable the new lazy load feature:

    The mobile menu at first appears on the top right, where it is supposed to appear. When reloading the page on mobile devices it moves below the logo on the left side.

    The issue disappears when I deactivate the lazy load feature. Is there anything I could do to have the mobile menu on the top right AND use the lazy load feature?

    Best regards and thank you
    Jasmin

    The page I need help with: [log in to see the link]

Viewing 13 replies - 16 through 28 (of 28 total)
  • Thread Starter jazzminus

    (@jazzminus)

    Yes, the issue persists if JS optimization is off. I installed the beta of 2.5.1 on https://spielwiese.packlisten.org. Unfortunately I see the same behaviour.

    I really appreciate your effort! If there is no solution to this, I will do without lazy load or try to use another plugin to lazy load images. ??

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    I’m not ready to give up yet ??

    Can you try adding below strings to the lazyload exclusion option to see if those make a difference;

    • svg
    • jpeg
    • png

    First add all of them (comma-separated) and if this fixes the weird issue try removing one (or two)?

    Thread Starter jazzminus

    (@jazzminus)

    I tried different combinations in the exclusion list:

    – svg, jpg, png: issue removed
    – svg: issue still there
    – svg, jpg: issue still there
    – svg, png: issue removed
    – png: issue removed
    – jpg: issue still there
    – jpg, png: issue removed

    So it seems that png is the decisive format. My logo is also png, but when I exclude only this file, the issue remains.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    ok, next up; try excluding

    • cropped-favicon
    • Packlisten-logo
    • Packlisten-Logo
    Thread Starter jazzminus

    (@jazzminus)

    – cropped-favicon –> issue remains
    – Packlisten-logo –> issue resolved
    – Packlisten-Logo –> issue resolved

    Does it search for this string? Because the filename of the logo is actually Packlisten-Logo-min.png. But excluding Packlisten-Logo-min or Packlisten-Logo-min.png doesn’t help.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    AO checks if the exclusion string is found in the <img tag, so could also be an id or a class. Maybe see if header-image also works?

    Thread Starter jazzminus

    (@jazzminus)

    No, with header-image the issue remains.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    then it must be Packlisten-logo-neu-60.png I guess? ??

    Thread Starter jazzminus

    (@jazzminus)

    Yes, that resolves the issue. So why doesn’t AO like this image? ??

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    So why doesn’t AO like this image?

    I *think* the issue is a bit more complex, as it only occurs in mobile on iOS (well, I haven’t been able to reproduce an Android or in a desktop browser emulating mobile at least). So it looks like the CSS applies differently on webkit (the basis of all iOS browsers) when lazyload is active on that image in the header. Maybe because that image is present twice in the HTML? ??

    Thread Starter jazzminus

    (@jazzminus)

    Ok, thank you very much, Frank, for your awesome support. I’ll let the Generatepress team know about the “problem file”. I should have tested excluding the floating logo earlier (Packlisten-logo-neu-60.png). I had only tested the main logo and some classes. But anyways, thank you!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    You’re welcome Jasmin, feel free to leave a review of the plugin and support here! ??

    And tell Tom of GeneratePress to reach out to me if he needs any input from me, I’ll be happy to help ??

    Thread Starter jazzminus

    (@jazzminus)

    It’s already done. ??

Viewing 13 replies - 16 through 28 (of 28 total)
  • The topic ‘Lazy loads lead to switching mobile menu’ is closed to new replies.