W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2010

[Bug 11295] Make script-inserted external scripts that have .async=false execute in the insertion order, default to true

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Dec 2010 07:00:26 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PYCUs-0003VT-Am@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11295

--- Comment #6 from Adam Barth <w3c@adambarth.com> 2010-12-30 07:00:25 UTC ---
> For what it's worth, my preference is to make .async default to false for
> elements created through the DOM. And make .async equals false mean that
> elements execute in order.

That would be a performance regression for WebKit, which is why we ended up
with this goofy property-not-reflecting-attribute scheme.

It would be helpful in figuring out what to do here if we had a list of sites
that don't work with the spec's current behavior.  I believe WebKit currently
matches the spec precisely in this regard, so those sites should presumably
break in the WebKit nightly.

-- 
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 Thursday, 30 December 2010 07:00:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:36 UTC