[whatwg] should async scripts block the document's load event?
jonas at sicking.cc
Sat Feb 13 16:22:29 PST 2010
On Sat, Feb 13, 2010 at 12:52 PM, Brian Kuhn <bnkuhn at 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
> execution blocks.
> So, it's pretty hard to say what web developers would expect with async
> scripts. I know that they will like having things like ads and analytics
> not block window.onload though. At the very least, we need that ability to
> make that happen.
Yeah, my big concern is "what do developers expect". Having an
explicit attribute for not blocking onload definitely follows the path
of least surprise. Though having an explicit attribute does give Steve
more things to evangelize, i.e. it'll probably lead to more pages
firing onload later than they could.
More information about the whatwg