[whatwg] DOMContentLoaded, load and current document readiness
ian at hixie.ch
Wed Aug 29 16:34:25 PDT 2012
On Sun, 17 Jun 2012, Jonas Sicking wrote:
> > On Wed, 25 Apr 2012, Jonas Sicking wrote:
> >> Hmm.. how long as that been the case? I thought that when we
> >> originally implemented @defer we ran them before DOMContentLoaded was
> >> fired for various internal sanity reasons as well as because it gave
> >> authors better migration paths.
> >> It seems nice to me to be able to depend on that all scripts have run
> >> by the time that DOMContentLoaded is fired. Except for async scripts
> >> of course, which are always unreliable as to when and which order
> >> they execute. I.e. async scripts is an explicit footgun, but I'd
> >> rather have fewer of those.
> > I haven't changed the spec here. I don't really see what we gain by
> > making the "stop parsing" algorithm different in this way.
> Different in what way? From what?
Different from what it says now in the way you propose above (having
appendChild-inserted <script src> element exection delay DOMContentLoaded).
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg