Closed Bug 140657 Opened 23 years ago Closed 21 years ago

Adjacent select tags combine into single select object

Categories

(Core :: DOM: HTML Parser, defect, P3)

x86
Windows 2000
defect

Tracking

()

RESOLVED FIXED
Future

People

(Reporter: chris.dawes, Assigned: harishd)

References

()

Details

(Keywords: compat, testcase)

Attachments

(1 file)

When this page is rendered it should render a select for each <SELECT> tag, however it combines all of the adjacent form fields of the same name into one select of with all the values within it. In other browsers it renders them correctly as separate select lists. I found this when I was writing a script that output the wrong thing, which looked fine until I tested in other browsers (hehe).
here's the .html file that is referred to in the url
seeing the same on linux build 20020426, also back to 0.9.7 ==> HTML Form Controls it seems like this probably done on purpose. Certainly, on the testpage, it is more useful to combine the elements into single selects.
Assignee: attinasi → rods
Component: Layout → HTML Form Controls
OS: Windows 2000 → All
QA Contact: petersen → tpreston
To parser. You have no </select> tags and it looks like we don't close out <select> elements automatically.... (note, per HTML4 we should not close them out).
Assignee: rods → harishd
Status: UNCONFIRMED → NEW
Component: HTML Form Controls → Parser
Ever confirmed: true
OS: All → Windows 2000
QA Contact: tpreston → moied
It works correctly with the </SELECT> tags inserted: As you can not nest <SELECT> tags, wouldn't it be sensible to close the previous tag? I would assume this would occur for all non-nestable tags? Please let me know if this is redundant thinking? I though this would be logical? I still think that this is a bug. I also think the argument is valid, even though it relies on bad code to prove the point.
Keywords: compat, testcase
Yes, for backwards compatibility we should probably autoclose SELECT.
Severity: major → normal
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.0.1
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Target Milestone: mozilla1.0.1 → Future
Similar issues to bug 171713
Depends on: 171713
Fixed by checkin for bug 171713.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: