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

[whatwg] should async scripts block the document's load event?

From: Steve Souders <whatwg@souders.org>
Date: Thu, 11 Feb 2010 22:23:39 -0800
Message-ID: <4B74F3EB.8050709@souders.org>
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 Kuhn<bnkuhn at 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 great if async scripts at
>> least had a way to not block that event.  It would help minimize the affect
>> that secondary-functionality like ads and web analytics have on the user
>> experience.
>> -Brian
>>      
> I'm concerned that this is too big of a departure from how people are
> used to<script>s behaving.
>
> If we do want to do something like this, one possibility would be to
> create a generic attribute that can go on things like<img>,<link
> rel=stylesheet>,<script>  etc that make the resource not block the
> 'load' event.
>
> / Jonas
>    
Received on Thursday, 11 February 2010 22:23:39 UTC

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