75630 - some <select> fields don't get submitted after a DOM manipulation

Status: VERIFIED WORKSFORME

(Core :: DOM: Core & HTML, defect)

Description

[Erich 'Ricky' Iseli]

Situation: On the linked page you have a basic relational database management
system. The drop down fields represent the foreign keys to other tables.

Problem: when you add several rows, fill them out and save the form, all <input>
values are sent back to the server, but only the <select>s of the first new row
are sent  (check out the URL to see what fields get submitted).

Explanation: when loading the page, a blank record is created. Before the field
names are defined to be unique (FIELDNAME_row), the whole <tr> is cloned via the
DOM. Every new record that is added is a new clone of the template record.

Extrapolation: though the <select> fields are visible, if they are a clone of a
clone, they are invisible to the form submission.

This is working correctly in IE 5.5, so this must be a Mozilla bug.

Comment 1

[Johnny Stenback (:jst)]

I don't see a problem with a build from last week (2001040404), what build do
you see this problem in, and exactly what are the steps to reproduce?

Comment 2

[Erich 'Ricky' Iseli]

I'm using build 2001-04-09-04.

The exact steps to reproduce are:

1) load the URL http://www.iseli.org/test/editdb.mv?edit=trans
2) click on "Append Record" so you have 2 blank lines
3) fill in all fields of these 2 blank rows, and select a value from the drop
down fields
4) click on "Save Changes"

Result:
All text fields but only the drop down fields of the first line get saved.

Expected results:
all fields get saved

Comment 3

[Erich 'Ricky' Iseli]

Huh? now it worked... That's very weird... I haven't changed the code and I was
using the same build. even other people tested it and saw the same problem.
Marking it WFM for now. but if problem comes back, I'll reopen.

Comment 4

[Prashant Desale]

Updating QA contact to Shivakiran Tummala.

Comment 5

[Sivakiran Tummala]

verified on win2k for build 2001-07-09-09