It can happen that other lazy-loading implementations are active (despite not being recommended), and the .no-js .lazy[data-src] CSS rule might cause them to disappear.
Possible Solution
The plugin should make sure to only hide images that were transformed by itself, and only images that use the JavaScript fallback (since only then, the .no-js selector will be relevant, since the noscript version would be shown).
Rename too generic lazy class to native-lazyload-js-fallback.
Only add that class to elements that use the fallback (and thus have a noscript variant).
Change CSS selector to .no-js .native-lazyload-js-fallback.
Issue Overview
It can happen that other lazy-loading implementations are active (despite not being recommended), and the
.no-js .lazy[data-src]CSS rule might cause them to disappear.Possible Solution
The plugin should make sure to only hide images that were transformed by itself, and only images that use the JavaScript fallback (since only then, the
.no-jsselector will be relevant, since thenoscriptversion would be shown).lazyclass tonative-lazyload-js-fallback.noscriptvariant)..no-js .native-lazyload-js-fallback.Related: https://wordpress.org/support/topic/images-not-visible-in-chrome-76/