incorrect scroll position (lazy load)

  • Resolved werdpres

    (@werdpres)


    5 years, 5 months ago

    if using the ToC to scroll, the page is scrolled to the correct position, however if i link externally to an anchor, the scroll position is way off

    this issue is not unique to this plugin

    i suspect the problem is the LiteSpeed caching plugin i use where i’ve enabled image lazy loading

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author LuckyWP

    (@theluckywp)

    Hello @werdpres !

    You understand right. This is problem of image lazy loading.

    Smooth scroll in our plugin work correctly with lazy loading.

    But if you use standart scroll to heading (disable smooth scroll or use other link) browser scroll page to heading (image don’t loaded), then lazy loading images and page gets bigger and position of heading changed.

    Thread Starter werdpres

    (@werdpres)

    hello!

    i did some testing and found that the problem was not lazy loading of images/iframes (LiteSpeed cache uses an image placeholder of the same size as the original image)

    the problem is with the LiteSpeed cache ‘Load CSS Asynchronously’ setting – when disabled, Lucky ToC scrolls to the correct page position from an external link

    this setting is found on the Settings > Optimize tab

    i don’t know if you can install this plugin for testing purposes unless your web server runs LiteSpeed

    Plugin Author LuckyWP

    (@theluckywp)

    With “Load CSS Asynchronously” the same behavior.

    Browser scroll page to heading (CSS don’t loaded), then CSS loading (changes block sizes, paddings, etc.) and page gets bigger and position of heading changed.

    Thread Starter werdpres

    (@werdpres)

    is this something that can be fixed?

    i should also mention that the scroll problem exists whether smooth scrolling is enabled or not

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘incorrect scroll position (lazy load)’ is closed to new replies.