- From: James Simonsen <simonjam@google.com>
- Date: Tue, 25 Jun 2013 15:05:19 -0700
- To: Simon Pieters <simonp@opera.com>
- Cc: public-web-perf <public-web-perf@w3.org>
Received on Tuesday, 25 June 2013 22:05:46 UTC
On Tue, Jun 25, 2013 at 2:59 PM, Simon Pieters <simonp@opera.com> wrote: > On Tue, 25 Jun 2013 22:27:09 +0200, James Simonsen <simonjam@google.com> > wrote: > > script >>> >>> This already has means to control when the script is executed (async and >>> defer). Since scripts are invisible, lazyload seems like the wrong >>> semantic. If the author wishes to load a script at a certain point, that >>> is >>> possible by creating and inserting a script at that point. >>> >>> >> The point is that it doesn't block the load event. You can specify >> everything in HTML, but not interfere with the critical path of the page >> load. An example use would be analytics, where it doesn't need to obstruct >> the page load and can load and run at an arbitrarily later time. >> > > This is already addressed by <script async>. Blink blocks the load event on <script async>. Is that a bug? It seems someone would've complained by now. http://stevesouders.com/cuzillion/?c0=hb0hfff0_1_t&t=1372197824038 Another thought: async begins loading immediately. Lazyload may start loading later at the browser's discretion. James
Received on Tuesday, 25 June 2013 22:05:46 UTC