Closed Bug 814064 Opened 12 years ago Closed 12 years ago

Don't fire onreadystatechange during async send()

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla20

People

(Reporter: bzbarsky, Assigned: bzbarsky)

Details

(Whiteboard: [CORS-testsuite])

Attachments

(1 file, 2 obsolete files)

We should not fire a readystatechange for our transition to the SENT state.
19.16 KB, patch
sicking
: review+
Details | Diff | Splinter Review 
We fire one when we shouldn't.
Er, I should run the other XHR tests... they might be depending on this behavior.  :(
Attached patch Now with more test passage (obsolete) — — Splinter Review 

        Attachment #684091 -
        Flags: review?(jonas)

    
  

        Attachment #684087 -
        Attachment is obsolete: true

        Attachment #684087 -
        Flags: review?(jonas)

    
  
Whiteboard: [need review] → [need review][CORS-testsuite]

    
  

        Attachment #684091 -
        Attachment is obsolete: true

        Attachment #684091 -
        Flags: review?(jonas)

    
    

    
  
https://hg.mozilla.org/integration/mozilla-inbound/rev/fd8f925ad459 with an additional worker test fix too.
Flags: in-testsuite+
Whiteboard: [need review][CORS-testsuite] → [CORS-testsuite]
Target Milestone: --- → mozilla20

    
    

    
  
https://hg.mozilla.org/mozilla-central/rev/fd8f925ad459
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: DOM → DOM: Core & HTML

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: