[Webkit-unassigned] [Bug 28328] javascript execution sequence.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Aug 15 11:30:23 PDT 2009


--- Comment #5 from Oliver Hunt <oliver at apple.com>  2009-08-15 11:30:21 PDT ---
(In reply to comment #4)
> (In reply to comment #3)
> > Here's a testcase -- firefox executes all the created script tags in the order
> > that they are attached to the document --
> > http://nerget.com/bugs/bug28328/index.html
> This isn't even THAT much of a problem, this would be acceptable in many cases.
> HOWEVER, if inclusion of script #2 is conditional upon the execution path of
> script #1, then you still see this "arbitrary" execution order. The execution
> of script #2 is started before the DOM work of script #1 is available to script
> #2, even though the addition of script #2 is a DOM change in itself.

The firefox behaviour was being given as an example of correct behaviour --
webkit executes the attached scripts in order of load completion it seems. 
This makes us different from all other browsers, and this behaviour has already
bitten me while working on one of my js demos.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list