372877 - On Windows Firefox 2.x only, DOM inserted scripts do not execute at the position they are inserted

Status: RESOLVED DUPLICATE of bug 371576

(Firefox :: General, defect)

Description

[Steve]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2

I have a dynamically (DOM) generated HTML login form, that lays on top (z-Index) of a page... (a la lightbox kind of deal).

The DOM contains (*GUI markup ignored):
- InputTextElement
- ScriptElement
- InputPasswordElement
- SubmitButtonElement
- CancelButtonElement

In the ScriptElement, I have inline calls to the effect of...

var fLen = document.forms.length;
var eLen = document.forms[fLen - 1].elements.length;
document.forms[fLen - 1].elements[eLen - 1].focus();

On Linux, or on Firefox 1.5.x, (and IE,Opera, etc.) this will place focus for me in the "username" field.

At some point in Firefox 2.x, the script execution moved to "after" the Cancel button, thus placing focus on the cancel button, instead of my username field.

I will attempt to submit a simple test case scenario... (after I extract the non-essential elements)




Reproducible: Always

Steps to Reproduce:
1. In Windows
2. In Firefox 2.x
3. Note when a DOM inserted script executes... it appears to execute after various "following siblings" have been rendered, not inline when the script content is being processed.
Actual Results:  
Script appears to execute after all sibling elements have been rendered.

Expected Results:  
inline script contents should be executed as parsed, and DOM insertion time.

Comment 1

[Steve]

Attachment: Test Case Showing broken behaviour

View this page in Firefox 1.5.x on Windows, and you will see it work... ditto for Firefox x.x on Linux, or IE, Opera, Konq, etc.

(*note some versions of Konq have some paint issues until another window goes over the dynamically inserted content, but that is another issue)

Note that in Firefox 2.x (I run 2.0.0.2 but I'm not sure which builds this affects), the text after the alert, is inserted before the alert is presented.