If you're using jQuery, I did something simple, yet effective, like this: View the pull request for the WHATWG specįallback JavaScript with notes about perhaps not using fallbacks You can use the same loading attribute with a value of eager to ask the browser to grab the image even if it might otherwise choose not to. Forced Eager LoadingĪutomatic lazy loading may become a feature of lightweight browsing, in which case, you may want to do the inverse and force an image to load.
That way, you can allow the native version to take over as it becomes available. If you are going to defer loading using a script, it would be worth writing the image with the lazy attribute and polyfilling the behavior as opposed to working off of a class name, etc. This is already in Chromium since v76, but might not hit non-Chromium browsers until it goes through the usual specification shennanigans. Setting the attribute to lazy invokes the new behaviour. This will defer loading of the content until the element reaches a calculated distance from the viewport (that just means, it's got quite likely that the user will scroll it into view).
The modern way to do this is with the loading attribute for images and iframes.
0 kommentar(er)
