I think we do not need library integration for the laizy loading because now the chrome developers have announced that it will be integrated direcetment in the browser. and that it is the browser that will detect the images to load or not. This integration will begin in version 75 of chrome. Other firefox developers have also announced that this will be integrated into the browser developed by mozilla.
You can read these articles to learn more
Chrome feature page for google: https://chromestatus.com/feature/5645767347798016
article that explains this feature:
https://css-tricks.com/native-lazy-loading/
https://addyosmani.com/blog/lazy-loading/
The loading attribute allows a browser to defer loading offscreen images and iframes until users scroll near them. loading supports three values:
lazy: is a good candidate for lazy loading.
eager: is not a good candidate for lazy loading. Load right away.
auto: browser will determine whether or not to lazily load.
This 'feature' maybe nice for Chrome users and also only for those who use the latest version only.
Which means: not useable at the moment (also because MSIE is not covered!), therefore a library is still needed.
Which means: not useable at the moment (also because MSIE is not covered!), therefore a library is still needed.
Full Stack Web Developer :: Dedicated OpenCart Development & Support DACH Region
Contact for Custom Work / Fast Support.
Who is online
Users browsing this forum: No registered users and 6 guests