Subject: Re: [whatwg] should async scripts block the document's load
event?
Right. Async scripts aren't really asynchronous if they block all the
user-visible functionality that sites currently tie to window.onload.
I don't know if we need another attribute, or if we just need
:* Friday, February 12, 2010 8:03 AM
*To:* Jonas Sicking
*Cc:* Steve Souders; WHAT Working Group
*Subject:* Re: [whatwg] should async scripts block the document's load
event?
Right. Async scripts aren't really asynchronous if they block all the
user-visible functionality that sites currently tie
On 2/13/10 9:29 AM, Darin Fisher wrote:
The Mozilla network code uses the phrase load background to describe a
load that happens asynchronously in the background _and_ does not block
onload. Perhaps not coincidentally, this mode is used to load
background images :-)
It used to be. It's not
FWIW, loading scripts asynchronously with the Script DOM Element approach
does not block window.onload in IE. In Chrome and Safari, the downloading
blocks, but execution doesn't. In Firefox and Opera, downloading and
execution blocks.
So, it's pretty hard to say what web developers would expect
On Sat, Feb 13, 2010 at 12:52 PM, Brian Kuhn bnk...@gmail.com wrote:
FWIW, loading scripts asynchronously with the Script DOM Element approach
does not block window.onload in IE. In Chrome and Safari, the downloading
blocks, but execution doesn't. In Firefox and Opera, downloading and
Right. Async scripts aren't really asynchronous if they block all the
user-visible functionality that sites currently tie to window.onload.
I don't know if we need another attribute, or if we just need to change the
behavior for all async scripts. But I think the best time to fix this is
now;
Subject: Re: [whatwg] should async scripts block the document's load
event?
Right. Async scripts aren't really asynchronous if they block all the
user-visible functionality that sites currently tie to window.onload.
I don't know if we need another attribute, or if we just need to change
[mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Brian Kuhn
Sent: Friday, February 12, 2010 8:03 AM
To: Jonas Sicking
Cc: Steve Souders; WHAT Working Group
Subject: Re: [whatwg] should async scripts block the document's load event?
Right. Async scripts aren't really asynchronous
Sicking
Cc: Steve Souders; WHAT Working Group
Subject: Re: [whatwg] should async scripts block the document's load event?
Right. Async scripts aren't really asynchronous if they block all the
user-visible functionality that sites currently tie to window.onload.
I don't know if we need another
I just sent email last week proposing a POSTONLOAD attribute for scripts.
-Steve
On 2/10/2010 5:18 PM, Jonas Sicking wrote:
On Fri, Nov 6, 2009 at 4:22 PM, Brian Kuhnbnk...@gmail.com wrote:
No one has any thoughts on this?
It seems to me that the purpose of async scripts is to get out of
Though what we want here is a DONTDELAYLOAD attribute. I.e. we want
load to start asap, but we don't want the load to hold up the load
event if all other resources finish loading before this one.
/ Jonas
On Thu, Feb 11, 2010 at 10:23 PM, Steve Souders wha...@souders.org wrote:
I just sent email
On Fri, Nov 6, 2009 at 4:22 PM, Brian Kuhn bnk...@gmail.com wrote:
No one has any thoughts on this?
It seems to me that the purpose of async scripts is to get out of the way of
user-visible functionality. Many sites currently attach user-visible
functionality to window.onload, so it would be
In section
4.3.1http://www.whatwg.org/specs/web-apps/current-work/#attr-script-async,
it says:
*Fetching an external script must delay the load event of the element's
document until the task that is queued by the networking task source once
the resource has been fetched (defined above) has been
13 matches
Mail list logo
