Closed Bug 188500 Opened 22 years ago Closed 22 years ago

Some DOM classes do not resolve

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla1.3beta

People

(Reporter: peterv, Assigned: peterv)

References

(
URL
)

Details

(Whiteboard: [whitebox])

Attachments

(1 file, 1 obsolete file)

v1
1.82 KB, patch
sicking
: review+
jst
: superreview+
Details | Diff | Splinter Review 
nsScriptNameSpaceManager::RegisterInterface only registers an interface if it
has constants as a performance optimization. However, this means that interfaces
not on the primary prototype chain never get registered. Personally, I think we
should just register all the DOM classes at startup, but maybe I'm missing
something?
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → mozilla1.3beta
Attached patch Proposal (obsolete) — — Splinter Review 

    
  
Whiteboard: [whitebox]

    
    

    
  

      
      
      
      

        Attached patch
          
          
        v1
        — 
          — Splinter Review
      

    


  

        Attachment #111172 -
        Attachment is obsolete: true

    
  

        Attachment #111515 -
        Flags: superreview?(jst)

        Attachment #111515 -
        Flags: review?(bugmail)

    
    

    
  
Comment on attachment 111515 [details] [diff] [review]
v1

sr=jst

        Attachment #111515 -
        Flags: superreview?(jst) → superreview+

    
    

    
  
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 22 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: