Any reasonable img lazyloading implementation should produce plain img tags once loaded. Not sure why you would end up with background-image’d block elements.
Re:Browsers are pretty good at loading pages
by yellowapple on Monday July 22, 2019 @11:14AM
(#20498757)
"once loaded" is the key. If it fails to load, then bummer, no img tag.
I'm also not sure about the background-image'd block elements, for what it's worth.
If it failed to load, it would leave behind an img tag that failed to load, like any non-lazy-loaded image. Unless you’re talking about JavaScript code failing to generate an img tag (e.g. from a data-src attribute), which would be bizarre.
Edit: by “once loaded” I meant once loading is triggered, if I wasn’t clear enough.
Given any browser, how do I reload a lazy-image that failed to load, without resorting to whole page refresh or diving deep into the Web Inspector?
Most browsers have a context menu option to reload regular images, but they cannot and will never handle a bunch of dynamic block elements with background-image option.