> > As far as images go, we could also say that the only reason we need hints > to lazyload images is the fact that Web compat requires image download > before onload. Authors could also provide a page-wide hint to say "I don't > care about images in my onload. You, the browser, can lazyload everything, > if you find it helpful". > That would complicate life for the preloader (no notion of viewport there, > so no idea which images are visible), but the download queue could then use > heuristics to download only the first X images, and wait for layout for the > rest, etc, etc. The browser is in a better position to do that. >
I was wondering if we had optional elements, then lazyloading of images would "just work": when an element is optional, its subtree is optional. Then under that subtree, we change the semantics of onload.
