[Boost] Dynamically loaded images don't have an image guide

[dilirity]

Impacted plugin

Boost

Steps to Reproduce

1. Install latest trunk version of Boost;
2. Enable Image Guide feature;
3. Install a plugin that allows an infinite load for images (for example Visual Portfolio, Masonry block);
4. Open the page and scroll down so more images get loaded;
5. The new images should not have the image guide bubble.

A clear and concise description of what you expected to happen.

Image Guide should work for dynamically loaded images as well.

What actually happened

Image Guide does not work on dynamically loaded images.

First three images are loaded on page load, the rest are on scroll.

Browser

Google Chrome/Chromium, Mozilla Firefox, Microsoft Edge, Apple Safari, iOS Safari, Android Chrome

Other information

No response

Platform (Simple, Atomic, or both?)

Simple

Reproducibility

Consistent

Severity

All

Available workarounds?

Yes, easy to implement

Workaround details

Currently, you can go around this by toggling the Image Guide from the admin bar on that page. Doing so will render the Image Guide for the dynamically loaded images.

[pyronaur]

I'll tackle this Monday alongside removing the always-on feature for now.

[pyronaur]

Ultimately, we might want to use a mutation observer (although we could just use a timer, I'm not too excited about that solution) to see when new images appear on the page and update the image guide accordingly.

But for the first version, I think we can release this as-is and observe how often are lazy images actually a problem for people using the feature.

[github-actions]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, `[Type] Feature Request`, `[Type] Enhancement`, `Good For Community`, `[Type] Good First Bug`, etc.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[sdixon194]

Did some more testing and looks like this one has been fixed already. Going to close the issue out, feel free to re-open if you're using it for some other kind of tracking.