294903 - impossible to find froms elements if forms tag inside a table tag...

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[yves]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 (ax)

If the tag forms is inside a table tag or a td tag is after impossible to
retreive the elements of the forms in javascript: 
document.forms.elements[x].name==undefined ???
It's works fine with IE and Opera, why not with Mozilla / Firefox familly.
It's a bug or we need to change more than 1000 templates ???


Reproducible: Always

Steps to Reproduce:
1.include a forms inside a table
2.try in javascript to retreived the elements values of this forms
3.but if you try document.getElementsByTagName, than it's possible to retreive
the information. So why not with the basic definition( document.forms).

Actual Results:  
impossible to retreived any information about the forms elements. always
undefined. If you alert the document.forms that the result is good but for an
element of the forms is always undefined.

Expected Results:  
like for IE and Opera, the name of the element of the value.
document.forms.elements[X].name
document.forms.elements[X].value
etc etc

Comment 1

[José Jeria]

Can you please attach a minimized testcase showing this issue?
https://bugzilla.mozilla.org/attachment.cgi?bugid=294903&action=enter

Comment 2

[yves]

Attachment: sample of code for this problem

Like you ask in your email. Sample of the page and the javascript function to
collect the forms informations.

Comment 3

[yves]

Attachment: here is the html code

Comment 4

[yves]

Attachment: js file

Comment 5

[José Jeria]

Can you please attach a minimial testcase with only one page containing the
necessary?

Comment 6

[José Jeria]

No reply from  reporter --> invalid

please reopen if you can reproduce with at least Firefox 1.5

Comment 7

[Jesse Ruderman]

Fwiw, this is probably a dup of bug 265976.