Closed Bug 72639 Opened 25 years ago Closed 25 years ago

Can't submit a form request

Categories

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

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla0.9

People

(Reporter: ezh, Assigned: harishd)

References

()

Details

1. Open the page 2. Try to select some city in the upper form 3. Press "go" 4. Nothing happens. 5. But the lower form works correctly moz 2001031904
The document defines two different forms with the same name ("worldcity"). Then it uses document.worldcity.europe to reference the first select and document.worldcity.europe_ntoz to reference the second select. This seems incredibly broken, but over to DOM0 to decide whether they want to support this weird NS4 behavior (NS4 does the "right" thing, obviously -- he form is submitted).
Assignee: rods → jst
Component: Form Submission → DOM Level 0
QA Contact: vladimire → desale
The problem with this site is that there's two <form name="worldcity"> tags on the page and the first one is never closed, so mozilla sees that as two form elements with the same name (the second one closes the first one, which IMO is a reasonable thing to do), IE seems to ignore the second form element and thus things work in IE. Mozilla things that document.worldcity is an array of two form elements. I talked to harishd about this and he said that mozilla could probably be changed easily to match what IE does, which is probably a good thing to do in the long run. Reassigning to harishd. I think that if we're gonna fix this we should do it soon, if we don't do it now we might as well leave it as is, the page is invalid after all. Harish, do you have time to experiment with this now?
Assignee: jst → harishd
Keywords: mozilla0.9, nsbeta1
OS: Windows 98 → All
Hardware: PC → All
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Should discard nested FORM. Fix is in. Marking FIXED.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Verified with 2001-08-28-08 on Win95.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.