W3C home > Mailing lists > Public > www-style@w3.org > July 2013

Re: lazy loading for images via css

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 2 Jul 2013 08:44:59 -0700
Message-ID: <CAAWBYDD+iy4UwFP6LMaKNqAso0VTfzcG_JSfWet2R5XXcT0DKg@mail.gmail.com>
To: Yoav Weiss <yoav@yoav.ws>
Cc: Simon Sapin <simon.sapin@exyr.org>, Liam Quin <liam@w3.org>, Felipe Nascimento de Moura <felipenmoura@gmail.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, www-style <www-style@w3.org>, brice@websailors.fr
On Tue, Jul 2, 2013 at 4:22 AM, Yoav Weiss <yoav@yoav.ws> wrote:
> A related standard proposal for HTML based resources can be found at
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourcePriorities/Overview.html
> Adding similar capabilities to CSS based resources, and especially
> background images and fonts (mainly for icon fonts), can be extremely useful
> for similar use-cases.
> In the Resource Priorities proposal the 'lazyload' attribute is used as a
> hint rather than a directive, and user agents should treat it as low
> priority resource (and load it after the other resources), but may load it
> regardless of its visibility (e.g. to avoid waking up the radio on mobile at
> a later phase).
> The only binding part in the Resource Priorities proposal is that 'lazyload'
> resources don't block the page's onload event.
> It seems logical to apply similar rules to CSS based resources that are
> marked for lazy loading.

Yes, I wouldn't intend it to be anything more than a hint that the
browser is allowed to load it "later": after all critical resources
but then otherwise unconstrained (except that they must load when they
come into view).

Received on Tuesday, 2 July 2013 15:45:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:32 UTC