• Resolved Anonymous User 14018805

    (@anonymized-14018805)


    The plugin presents compatibility issues with a3 lazy load.

    Pratically the blocks are broken when activating lazy load scripts

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi @blackster000, unfortunately they can’t account for how plugins conduct lazy loading. If it’s breaking the images in these galleries, it’s likely doing the same across any plugins that utilize masonry/flickity carousels.

    • This reply was modified 5 years, 6 months ago by shopomatic.
    Plugin Author Rich Tabor

    (@richtabor)

    That’s correct. ??

    Thread Starter Anonymous User 14018805

    (@anonymized-14018805)

    so would be possible to exclude only homepage from lazy loading?

    thank you

    Hey there,
    sorry if the thread it’s kind of old, but the problem still exists, and is kind of important too, and TBH it’s not exclusive to block gallery, lot’s of other masonry/carrousel plugins have exactly the same problem, and the same goes a3 lazy load, most, if not all of the plugins fail to manage Block’s Gallery lazy loading 100% correctly.
    What could be really helpful, and probably easy, would be that block gallery added an specific class to every Block Gallery image (img object), so we could at least use lazy loading with every other image and just exclude block gallery’s ones from lazy load (a feature most lazy load plugins have), and preferably (tbh I think it’s really important too) in a way that it works also with all the gallerys we already have created before and not only with the new ones.

    Thanks in advance

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Compatibility issues with a3 lazy load’ is closed to new replies.