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)

Product:
Core
Component:
Layout: Form Controls
Platform:
PowerPC
Mac System 8.5
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: rwoods, Assigned: rods)

Details

(Whiteboard: Fix in my tree)

Attachments

(1 file)

testcase showing incorrect behavior
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.

    
    

    
  
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

    
    

    
  
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

    
    

    
  
fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED

    
    

    
  
Updating QA contact.
QA Contact: ckritzer → bsharma

    
    

    
  
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.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: