The "lazy loading" mechanism has been added in order to prevent images to load when they won't be displayed (some people appreciate faster loading and smaller bandwidth footprint, especially on mobile devices).
It was working fine.. I'm investigating what changed.
Valentin
added a comment - The "lazy loading" mechanism has been added in order to prevent images to load when they won't be displayed (some people appreciate faster loading and smaller bandwidth footprint, especially on mobile devices).
It was working fine.. I'm investigating what changed.
Actually, the browser will load all resources as it discovers them in the HTML - regardless of their visibility in the viewport (some huge images might then load and "block" the rendering process - which leads to a laggy experience).
Anyways.. it should be now fixed.
The problem came from a style which defined negative margins and therefore screwed the bounding box computation...
¯\ _(ツ)_ /¯
Valentin
added a comment - Actually, the browser will load all resources as it discovers them in the HTML - regardless of their visibility in the viewport (some huge images might then load and "block" the rendering process - which leads to a laggy experience).
Anyways.. it should be now fixed.
The problem came from a style which defined negative margins and therefore screwed the bounding box computation...
¯\ _(ツ)_ /¯
Also why do we need javascript to display images in the blog?