W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2011

[Bug 12049] Script defer/async attributed have no realistic usage scenario

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Feb 2011 23:56:09 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PsOYz-0000G2-Uw@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12049

--- Comment #6 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-02-23 23:56:09 UTC ---
(In reply to comment #5)
> Again, assuming most users don't have a clue regarding script order, and don't
> really have any means to do it correctly,
> especially with scripts that are externally-sourced and thus have dynamic
> loading performance, the solution is to assume
> all scripts are deferrable, unless they depend on a non-defined function
> evokation.

There are zillions of ways JavaScript files can depend on each other other than
function calls.  For instance, one might set a variable that the other one
later checks.  One might modify the state of the page in a way a later script
depends on, like changing some existing property of document or window or
modifying the DOM.  There's no way to detect this kind of dependency if you run
the scripts out of order.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 23 February 2011 23:56:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 23 February 2011 23:56:21 GMT