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

Re: [ResourcePriorities] Only specify lazyload on img

From: James Simonsen <simonjam@google.com>
Date: Tue, 25 Jun 2013 15:05:19 -0700
Message-ID: <CAPVJQincBguLwn71bCM12jEmfz_Kzmb9b=5_6CVdVZHE-S5KZg@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: public-web-perf <public-web-perf@w3.org>
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.


Another thought: async begins loading immediately. Lazyload may start
loading later at the browser's discretion.

Received on Tuesday, 25 June 2013 22:05:46 UTC

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