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

[Brian Kuhn]

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



On Tue, Nov 3, 2009 at 12:55 PM, Brian Kuhn <bnkuhn at gmail.com> wrote:

> In section 4.3.1<http://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 run.*
>
> Has any thought been put into changing this for async scripts?  It seems
> like it might be worthwhile to allow window.onload to fire while an async
> script is still downloading if everything else is done.
>
> Thanks,
>     Brian
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20091106/7f4864d7/attachment.htm>