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

> '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.

I think you have a good point here. 'delayload' delays downloading the resource but does not delay the window load event is confusing. 'lazyload' does seem to not have that problem and may be a more well understood term (for what it's worth, it has a Wikipedia page: http://en.wikipedia.org/wiki/Lazy_loading).

What do folks think of the 'lazyload' term?

I also think the spec should be clear that using this attribute will mean that this resource will not block the load event for the window, but will continue to block the load event for itself.

Thanks,
Jatinder

From: jakearchibald@google.com [mailto:jakearchibald@google.com] On Behalf Of Jake Archibald
Sent: Wednesday, May 22, 2013 8:26 AM
To: Jatinder Mann
Cc: public-web-perf@w3.org
Subject: Re: <img src="..." defer>

On Tue, May 21, 2013 at 9:09 PM, Jatinder Mann <jmann@microsoft.com<mailto: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