Compatible or being replaced with lazy load initiative?

If you have more links like "Slated", roadmaps, or scopes, please update summary so to have more resources about what changes should be followed up at Blazy.

I am not sure about depreciation by just one attribute change?

Based on the referenced issue, it was meant to limit-scope to adopt native [loading] attribute for major browsers without degrades.

Unless it grows, of course.

Depreciation might happen if it superceded or covered 90% features (aspect ratio, lightboxes, carousel, masonry grid, fullscreen video, graceful degradation for oldies, media player etc.). All cosmetics, and the little details that Blazy has to offer with contrib integrations, colorbox, carousel, svg, animate.css, etc. are less likely entering core.

I can be wrong. But when proven wrong, that should make us happy then, less things to look after.

Regarding compatibility, we did have 3 raised objections with few more amens at Blazy issues against this particular [loading] attribute being printed without an option which appears to be the case at that thread as of this writing.

We can tune as needed. We should at least identify and drop or adjust features which are already taken care of by core if it grows beyond the initial scope.

I haven't been able to find out more details about its roadmap or latest scopes.

Feel free to share your findings or patches.

Thank you.

I'm following that development and like it.

While loading=lazy has been there for some time, now that
- Wordpress leverages it and
- ALL browsers except IE soon have it and
- microsoft pushes edge instead of IE even for old systems

... i guess we can really soon completely rely on loading=lazy.
It's just tiny patches in core and contrib to add the attribute by default.

So how long it takes to supersede this module noone knows, but soon-ish it will.

Yes, for now the initiative is focused on a very minimal change to add the default attribute. There will likely continue to be room for additional modules to provide other options and more control for a long time to come.

A friendly housekeeping here before a new release.

> There will likely continue to be room for additional modules to provide other options and more control for a long time to come.

Thank you for your confirmation. I guess we can close this, then. Also based on #2 particular paragraph:
> Depreciation might happen if it superceded or covered 90% features (aspect ratio, lightboxes, carousel, masonry grid, fullscreen video, graceful degradation for oldies, media player etc.). All cosmetics, and the little details that Blazy has to offer with contrib integrations, colorbox, carousel, svg, animate.css, etc. are less likely entering core.

Marking this fixed for another 2 weeks visibility instead.