I don't know... to me, "asynchronous" means completes later. Precedence: XMLHttpRequest.<div><br></div><div>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 :-)</div>
<div><div><br></div><div>-Darin</div><div><br><br><div class="gmail_quote">On Fri, Feb 12, 2010 at 11:50 AM, Jonas Sicking <span dir="ltr"><jonas@sicking.cc></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It's a good point. Curious to hear what other people are thinking.<br>
<font color="#888888"><br>
/ Jonas<br>
</font><div><div></div><div class="h5"><br>
On Fri, Feb 12, 2010 at 10:10 AM, Nicholas Zakas <<a href="mailto:nzakas@yahoo-inc.com">nzakas@yahoo-inc.com</a>> wrote:<br>
> To me “asynchronous” fundamentally means “doesn’t block other things from<br>
> happening,” so if async currently does block the load event from firing then<br>
> that seems very wrong to me.<br>
><br>
><br>
><br>
> -Nicholas<br>
><br>
><br>
><br>
> ______________________________________________<br>
><br>
> Commander Lock: "Damnit Morpheus, not everyone believes what you believe!"<br>
><br>
> Morpheus: "My beliefs do not require them to."<br>
><br>
> ________________________________<br>
><br>
> From: <a href="mailto:whatwg-bounces@lists.whatwg.org">whatwg-bounces@lists.whatwg.org</a><br>
> [mailto:<a href="mailto:whatwg-bounces@lists.whatwg.org">whatwg-bounces@lists.whatwg.org</a>] On Behalf Of Brian Kuhn<br>
> Sent: Friday, February 12, 2010 8:03 AM<br>
> To: Jonas Sicking<br>
> Cc: Steve Souders; WHAT Working Group<br>
> Subject: Re: [whatwg] should async scripts block the document's load event?<br>
><br>
><br>
><br>
> Right. Async scripts aren't really asynchronous if they block all the<br>
> user-visible functionality that sites currently tie to window.onload.<br>
><br>
><br>
><br>
> I don't know if we need another attribute, or if we just need to change the<br>
> behavior for all async scripts. But I think the best time to fix this is<br>
> now; before too many UAs implement async.<br>
><br>
><br>
><br>
> -Brian<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On Thu, Feb 11, 2010 at 10:41 PM, Jonas Sicking <jonas@sicking.cc> wrote:<br>
><br>
> Though what we want here is a DONTDELAYLOAD attribute. I.e. we want<br>
> load to start asap, but we don't want the load to hold up the load<br>
> event if all other resources finish loading before this one.<br>
><br>
> / Jonas<br>
><br>
> On Thu, Feb 11, 2010 at 10:23 PM, Steve Souders <<a href="mailto:whatwg@souders.org">whatwg@souders.org</a>> wrote:<br>
>> I just sent email last week proposing a POSTONLOAD attribute for scripts.<br>
>><br>
>> -Steve<br>
>><br>
>> On 2/10/2010 5:18 PM, Jonas Sicking wrote:<br>
>>><br>
>>> On Fri, Nov 6, 2009 at 4:22 PM, Brian Kuhn<<a href="mailto:bnkuhn@gmail.com">bnkuhn@gmail.com</a>> wrote:<br>
>>><br>
>>>><br>
>>>> No one has any thoughts on this?<br>
>>>> It seems to me that the purpose of async scripts is to get out of the<br>
>>>> way<br>
>>>> of<br>
>>>> user-visible functionality. Many sites currently attach user-visible<br>
>>>> functionality to window.onload, so it would be great if async scripts at<br>
>>>> least had a way to not block that event. It would help minimize the<br>
>>>> affect<br>
>>>> that secondary-functionality like ads and web analytics have on the user<br>
>>>> experience.<br>
>>>> -Brian<br>
>>>><br>
>>><br>
>>> I'm concerned that this is too big of a departure from how people are<br>
>>> used to<script>s behaving.<br>
>>><br>
>>> If we do want to do something like this, one possibility would be to<br>
>>> create a generic attribute that can go on things like<img>,<link<br>
>>> rel=stylesheet>,<script> etc that make the resource not block the<br>
>>> 'load' event.<br>
>>><br>
>>> / Jonas<br>
>>><br>
>><br>
><br>
><br>
</div></div></blockquote></div><br></div></div>