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

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

From: Jatinder Mann <jmann@microsoft.com>
Date: Tue, 21 May 2013 20:09:28 +0000
To: "'public-web-perf@w3.org'" <public-web-perf@w3.org>
Message-ID: <6c72f3c6a4a943e4a5dcea83d348585c@BLUPR03MB065.namprd03.prod.outlook.com>
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. Other names suggested on the mailing list were 'lazy', 'lazyload', and 'defer'. Considering 'defer' is already defined for script elements to mean do not execute until the document has been parsed, and we want this new attribute to not block the load event due to the specified resource, using 'defer' has a compatibility risk for existing scripts. E.g, 'defer' scripts that are already called in the load event may not be downloaded by that time. I recommend we instead use the attribute name 'delayload'. This name is very clear that the attribute will delay loading the lower priority resource.

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.

I have updated the draft doc [1]. Thoughts on these changes?


[1] https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourcePriorities/Overview.html
Received on Tuesday, 21 May 2013 20:13:55 UTC

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