W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2011

[whatwg] Proposal for separating script downloads and execution

From: Nicholas Zakas <nzakas@yahoo-inc.com>
Date: Thu, 17 Feb 2011 08:07:38 -0800
Message-ID: <B66541E954ECF146AD8CA69D34A283FF2822394CBC@SP2-EX07VS02.ds.corp.yahoo.com>
With regards to #1, I do think it could be user-agent defined if agreement can't be reached on the correct default behavior (so in IE preload would default to true while in FF it would default to false). That seems like a reasonable first step.

CCing Boris to see if the implementation would be too horrible to consider.


From: serverherder@gmail.com [mailto:serverherder@gmail.com] On Behalf Of Will Alexander
Sent: Wednesday, February 16, 2011 9:29 AM
To: Nicholas Zakas
Cc: Glenn Maynard; Will Alexander; whatwg at lists.whatwg.org; Kyle Simpson; Steve Souders
Subject: Re: RE: [whatwg] Proposal for separating script downloads and execution

On Feb 15, 2011 6:34 PM, "Nicholas Zakas" <nzakas at yahoo-inc.com<mailto:nzakas at yahoo-inc.com>> wrote:
> 1) Should the default behavior for dynamic script nodes be to start downloading the file upon the setting of src and only execute when added to the document (IE's behavior) or not?

Could the default behavior be defined by the user-agent and the value of this property reflect that?  So in IE the def value would be true, but false in other browsers.

> 2) Can the proposals on the table be used to better detect the correct behavior from #1?

> 3) Are the proposals close to being feasible with, perhaps, some changes? Or are they completely outlandish and have no possibility of reaching implementation?

In this bug report Boris Zbarsky expresses concern that prefetching without creating memory leaks is difficult.


Received on Thursday, 17 February 2011 08:07:38 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:30 UTC