Slashdot Mirror
Google Chrome To Feature Built-In Image Lazy Loading (bleepingcomputer.com)
An anonymous reader writes: Future versions of Google Chrome will feature built-in support for lazy loading, a mechanism to defer the loading of images and iframes if they are not visible on the user's screen at load time. This system will first ship with Chrome for Android and Google doesn't rule out adding it to desktop versions if tests go as planned. The feature is called Blink LazyLoad, and as the name hints, it will implement the principle of "lazy loading" inside Chrome itself.
Google engineers reported page load speed improvements varying from 18% to 35%, depending on the underlying network. Other browser makers have been notified of the Chrome team's plan, but none have provided input if they plan to implement a similar feature. Compared to most JS-based lazy loading scripts that only target images, Google implementation will also target iframes.
Google engineers reported page load speed improvements varying from 18% to 35%, depending on the underlying network. Other browser makers have been notified of the Chrome team's plan, but none have provided input if they plan to implement a similar feature. Compared to most JS-based lazy loading scripts that only target images, Google implementation will also target iframes.
You do realize that this is how the web is supposed to be, right? Web developer develops a page, the browser determines how to render the page. This is exactly how things are supposed to be.
Just to elaborate a bit more as you are apparently slow, the first freaking sentence of your link says "*User agents are not required to present HTML documents in any particular way. ".
This is an important part of the way the web is supposed to work. You see way back n the day, the founders of the web understood that people would be viewing the web on different hardware, and in the future it would be viewed differently. Some folks might be sight imparted and be using readers. Some would not be able to support graphics, some may be limited in other ways. HTML was the language sent to the browser and the browser would be responsible for HOW to display it.
Yes, we now support CSS and with the introduction of CSS3, the server is able to suggest (note, not control) how a page is laid out. If a browser chooses to ignore one of the W3C's suggestions, it is free to. Really, this is by design. It is not a flaw. So if your browser chooses to render images that aren't displayed immediately, it is free to. If it chooses to not render them, that is also fine.
Web developers really need to understand this. It is one of the underlying tenets of the web and it really, really makes me sad when folks who make their living doing this stuff just don't get it.