Re: [ResourcePriorities] Spec updates

On Tue, Aug 20, 2013 at 4:09 PM, Jatinder Mann <jmann@microsoft.com> wrote:
> 
> Based on feedback from the working group, I have made some updates to the
> Resource Priorities spec,
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourcePriorities/Overview.
> html:
>  
> -          Added the postpone attribute
> 
> The use case of never downloading a resource until its viewable by the user
> seems compelling from a system resources, server resources, and user bandwidth
> (e.g., mobile user) scenarios, but it does feel functionally different from
> the lazyload concept, where in cases of network contention connections are
> given to higher priority resources. I¹ve added a new postpone attribute to
> describe the case where we don¹t want resources to be downloaded if they
> aren¹t formatted to be visible or are not in the viewport. This attribute only
> applies to resources that can be laid out.

I came across a post by Mika Tuppola on Andy Davies' blog which makes a
valid semantic point,
and apparently hasn't been put forward in this list. I'll just quote it, as
it is self explanatory:

"I have a feeling that W3C is mixing the definition of lazyload and
postpone. Lazyload is programming technique of deferring loading of an
object until it is actually needed. Definition of postpone is to cause or
arrange for something to take place at a time later than first scheduled.
Reading the Resource Priorities draft they describe lazyload as postponing
and vice versa."


http://andydavies.me/blog/2013/10/22/how-the-browser-pre-loader-makes-pages-
load-faster/#comment-1094293686