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

Re: Executing script-inserted external scripts in insertion order

From: Getify <getify@gmail.com>
Date: Mon, 18 Oct 2010 00:28:15 -0500
Message-ID: <E7108AE6D8D54131A8636107D600A85D@spartacus>
To: "Adam Barth" <w3c@adambarth.com>, "public html" <public-html@w3.org>
?> That seems like an independent question from whether we fetch scripts
> with non-executable MIME types.

I was addressing your assertion that the proposal is going to lead to slower 
scripts in IE/Webkit. It won't lead to "slower scripts on most sites" 
because my proposal says the default should be `async=true` for 
script-inserted scripts, which should be how they currently work in those 

This has nothing to do with the question of the non-executable MIME types. 
The only reason why the non-executable MIME types has been brought up is 
because this "preloading" hack was how LABjs worked in Webkit up to now. Now 
that it's been changed in Webkit, it makes the resolution of this proposal 
even more important because, at the moment, LABjs cannot do ANY preloading 
at all in Webkit, which effectively kills the 99% reason why LABjs even 

I'm *NOT* arguing that the non-executable MIME types should be brought 
back -- I never liked the hack anyway. I'm simply pointing out that the 
change forces the hand and causes this to be a bigger problem for LABjs than 

> How does that solve Firefox's
> problem?  Why would they be able to implement that but not implement
> what the spec currently says?

Again, not sure why we're getting confused here. There are two separate 
changes, one made by Mozilla/FF and one made by Webkit. The two changes are 
pretty much unrelated, except for the fact that both of them break LABjs in 
the respective browser, though in different ways.


Received on Monday, 18 October 2010 05:28:52 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:06 UTC