W3C home > Mailing lists > Public > public-web-perf@w3.org > May 2013

Re: <img src="..." defer>

From: Jake Archibald <jakearchibald@chromium.org>
Date: Wed, 22 May 2013 16:25:34 +0100
Message-ID: <CAPy=Jopy6TKm6qoiw-=J1QvL2O=zXQJWcZduHWyFt2Zt7V=nzg@mail.gmail.com>
To: Jatinder Mann <jmann@microsoft.com>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
On Tue, May 21, 2013 at 9:09 PM, Jatinder Mann <jmann@microsoft.com> wrote:

>  Based on discussions with web developers, the attribute name ‘delay’
> doesn’t seem clear and can carry the wrong connotations that the attribute
> is slowing down the page load
>
…I recommend we instead use the attribute name ‘delayload’. This name is
> very clear that the attribute will delay loading the lower priority
> resource.
>

I imagine developers will react the same to 'delayload' as they do to
'delay', although I'm just guessing.

'delayload' as in 'delay the load' sounds like the image may delay the
loading of the page, when (in terms of the load event of the document) it
does the opposite.

'lazy' or 'lazyload' sounds more like it's only impacting the image,
perhaps because it's an existing term and used frequently in relation to
image loading.


> Also, as XHRs can just be deprioritized through script and they are the
> only non-element on the list, I recommend we just remove them.
>

+1
Received on Wednesday, 22 May 2013 19:31:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:35 UTC