No one has any thoughts on this? <div><br></div><div>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.</div>
<div><br></div><div>-Brian </div><div><br></div><div><br><br><div class="gmail_quote">On Tue, Nov 3, 2009 at 12:55 PM, Brian Kuhn <span dir="ltr"><<a href="mailto:bnkuhn@gmail.com">bnkuhn@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">In <a href="http://www.whatwg.org/specs/web-apps/current-work/#attr-script-async" target="_blank">section 4.3.1</a>, it says:<div>
<br><i><font color="#CC0000">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.</font></i><br>
<br><div>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.</div><div>
<br></div><div>Thanks,</div><div> Brian</div><font color="#888888"><div><br></div><div> </div></font></div>
</blockquote></div><br></div>