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 08:33:38 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PYDx4-0001Sz-Ec@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11295

--- Comment #7 from Maciej Stachowiak <mjs@apple.com> 2010-12-30 08:33:37 UTC ---
(In reply to comment #6)
> > 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.

WebKit historically hasn't had an order guarantee for DOM-inserted scripts, and
sites would UA sniff and use a different technique.

-- 
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 08:33:40 UTC

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