[FIX]Can't set value of non-empty OPTION element to null

VERIFIED FIXED

Status

()

Core
Layout: Form Controls
P3
normal
VERIFIED FIXED
18 years ago
17 years ago

People

(Reporter: rwoods, Assigned: rods (gone))

Tracking

Trunk
PowerPC
Mac System 8.5
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: Fix in my tree)

Attachments

(1 attachment)

(Reporter)

Description

18 years ago
<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.
(Reporter)

Comment 1

18 years ago
Created attachment 7763 [details]
testcase showing incorrect behavior
(Assignee)

Comment 2

18 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

18 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

18 years ago
fixed
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 5

18 years ago
Updating QA contact.
QA Contact: ckritzer → bsharma

Comment 6

17 years ago
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.