David Higgins

I just ran into a similar issue, where my theme includes a lot of hard-coded tags.

Adding the “native-lazyload-js-fallback” class to them all seems a bit excessive, and unnecessary.

A quick tweak to the “querySelectorAll” in the nativeLazyLoadIntialize scripts in the fallback seems to do the trick.

What I’d like to be able to do is register or override that querySelectorAll( '.native-lazyload-js-fallback' ) with a filter. This would allow me to pass img[loading] as an alternative, to catch all the <img loading="lazy" data-src="path/to.jpg" />

The auto-populated value in the media editor was causing problems with my users. They saw an input field with a value, and then attempted to remove the value.

if the value being added to the input is “virtual”, then it should be set as a placeholder. This way there is no actual value in the field, just a “virtual placeholder”.

I guess it’s more of a User Experience issue?

I have the same problem. This shows up immediately after updating, when WP_DEBUG is turned on.

addthis_social_widget.php:1337

Seems to only be an issue when you have “I want to control my plugin from…” set to WordPress.