298912 - Internal error not visible on JS console in number ordering while operating on DOM input fields through JavaScript

Status: RESOLVED DUPLICATE of bug 204784

(Firefox :: General, defect)

Description

[siersc]

User-Agent:       Opera/8.01 (Windows NT 5.1; U; en)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl-PL; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

I attach you the xhtml 1.0 code with embedded JavaScript.
The problem is that if you create HTML form and refer to its input fields through 
Javascript, internal error occurs when you set property "type" of document.forms[0
].element[x] that is 'input field'. THIS ERROR IS INVISIBLE IN JS CONSOLE.
To show it I ordered embedded script to fill all input fields ('onload') with increasing 
values. if "type" property is not set in JS, no error occurs. If you remove leading 
slashes (comments) from the line marked with "*", and reload the page, the fields 
will not be filled correctly (!).

Reproducible: Always

Steps to Reproduce:
1. run attached html+JS code
2. look at the site, the input fields are filled with increasing numbers (0,1,2,3,4).
3. remove leading '/' [comments] from line marked with "*"
4. reload the page and look at input fields. you may try to reload it few times it is 
another configuration after each page reload.

Actual Results:  
WRONG ORDER OF NUMBER IN INPUT FIELDS

Expected Results:  
I run this code on Opera 7,5 and 8.01, IE 6, IE 6SP2. Only in firefox it seem to be 
buggy.

Comment 1

[siersc]

Attachment: XHTML 1.0 + embedded Java Script to show DOM internal error while operating on "type" property of input field.

Load the attachment into browser and read instructions (XHTML1.0+JS).
Problem described in general information about bug and in attached code.
The code above I used in my WWW page within tables.

Comment 2

[Erik Fabert]

WFM in Deer Park Alpha 1. I guess this was bug 204784.

*** This bug has been marked as a duplicate of 204784 ***

Comment 3

[siersc]

(In reply to comment #2)
> WFM in Deer Park Alpha 1. I guess this was bug 204784.
> 
> *** This bug has been marked as a duplicate of 204784 ***

"This is comment ffrom descrip>tion of BUG 204784:
>> The following line should say 'xyz'. If it does not, it means that the 
>> elements in the form.elements[] array are not order perserving when using 
>> the javascript DOM interface."

In my example there is no problem with order of elements, because order is 
preserved. (I can make instructions in JS like: "docu.forms[0].elements[1]=..." 
and it will work).
The problem seem to be assigning any TYPE to the "input" field. Removing of that 
instruction makes the scripts to work properly...
Nevertheless if you find it the same problem as the BUG 204784, I give up.

Comment 4

[Erik Fabert]

Attachment: Testcase, modified

I'm convinced this is just another effect of bug 204784. Look at this modified
version of your testcase, it demonstrates that the element order is _not_
preserved in FF 1.04. 
If you don't agree, please test this again in Deer Park Alpha 1 and if you can
still reproduce this problem then reopen this bug. If you can't reproduce it
then please change the resolution to WORKSFORME.