You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chrome is implementing a loading attribute for images and iframes which can then be set to lazy to have it natively lazy load the element with JS then only being required for browsers without the feature (with it then having feature detection to help determine if the JS code is needed or not).
Either way, I’m thinking this could be the next step in improving this functionality and being one of the first plugins to support it (while having the nice existing JS fallback) could be a nice differentiator. Also, it seems like implementing this wouldn’t be too terribly time intensive.
@KZeni Thanks for feature request , i really like that feature, will have look and see if we can add it on next version, we are converting plugin to Composer autoload , also more security with sanitize inputs and esc outputs
Chrome is implementing a
loading
attribute for images and iframes which can then be set tolazy
to have it natively lazy load the element with JS then only being required for browsers without the feature (with it then having feature detection to help determine if the JS code is needed or not).You can see more about this here: https://addyosmani.com/blog/lazy-loading/
Also, https://chromestatus.com/feature/5645767347798016 shows that Safari is interested in adopting the feature as well as providing a placeholder to show until the element’s loaded (exact comment on the matter is here: whatwg/html#2806 (comment))
Either way, I’m thinking this could be the next step in improving this functionality and being one of the first plugins to support it (while having the nice existing JS fallback) could be a nice differentiator. Also, it seems like implementing this wouldn’t be too terribly time intensive.
I also mentioned this at https://wordpress.org/support/topic/feature-request-add-native-loadinglazy-support/, but I figured I'd mention it here for more development visibility.
Thanks for the great plugin,
Kurt
The text was updated successfully, but these errors were encountered: