Closed
Bug 36459
Opened 24 years ago
Closed 24 years ago
[FIX]Can't set value of non-empty OPTION element to null
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: rwoods, Assigned: rods)
Details
(Whiteboard: Fix in my tree)
Attachments
(1 file)
930 bytes,
text/html
|
Details |
<OPTION value="">b</OPTION> in a SELECT element results in an initial value of 'b' rather than null. This would be correct if the value attribute were omitted, but when a null value is explicity set, the value should not default to the option's contents.
Assignee | ||
Comment 2•24 years ago
|
||
Yes, we are currently check to see if the return value is empty and then get the label and then the content. We need to check to see if the attr exists instead of checking to see if it empty.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee | ||
Comment 3•24 years ago
|
||
need to use the nsIHTMLContent interface to check to see if the attr exists first.
Summary: Can't set value of non-empty OPTION element to null → [FIX]Can't set value of non-empty OPTION element to null
Whiteboard: Fix in my tree
Assignee | ||
Comment 4•24 years ago
|
||
fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified build 2001080108T os:Linux7.1,mac8.6
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•