|
|
|
|
|
by city41
2488 days ago
|
|
The article contradicts itself a little bit. It says "Currently the images are fetched with different priority in Chrome, the ones which are not in the viewport have less priority. But they're fetched as soon as possible regardless." But it also says: "lazy: Defer loading of resources until it reaches a calculated distance from viewport." If a lazy image is only loaded when within a distance of the viewport, then your "come back later" strategy stops working. But if instead off screen images are just bumped down in priority and still download after higher priority stuff finishes, then your strategy should still work. |
|