W3C home > Mailing lists > Public > public-html@w3.org > October 2010

Re: Executing script-inserted external scripts in insertion order

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Mon, 18 Oct 2010 00:13:42 -0400
Message-ID: <4CBBC976.1070406@mit.edu>
To: Adam Barth <w3c@adambarth.com>
CC: Getify <getify@gmail.com>, public html <public-html@w3.org>
On 10/17/10 11:59 PM, Adam Barth wrote:
> Can you provide examples of sites that break?

He already did earlier in this thread, no?

>> I think it even further underscores the need for a spec change (that all the
>> browsers can agree on) which gives a reliable and straightforward answer to
>> "parallel-load-serial-execute" use case in a performance-oriented and
>> feature-testable way.
>
> Isn't this what defer does?

No, because that defers the scripts to onload.  The goal here is to 
execute a set of scripts as soon from now as possible, but in a 
particular order.

>> Since Webkit has made this change that is in a non-compat way with existing
>> content, are they willing to support the proposed change as a
>> feature-testable addition (to spec and the browsers) that provides an answer
>> to the use-case?
>
> I believe tonyg said that he thought the proposed change would slow
> down a bunch of real-world web sites that use script-inserted scripts
> to achieve parallel loading in existing browsers.

1)  Which change(s) are we talking about here??  There are at least 3 
mutually exclusive proposed changes at this point, I think.

2)  I'd be interested in mention of actual sites that are slowed down by 
the changes in question (esp. the one where async is just allowed to 
apply to script-inserted stuff.

-Boris
Received on Monday, 18 October 2010 04:14:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:15 GMT