This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15695 - Should MutationCallback be a callback *interface*?
Summary: Should MutationCallback be a callback *interface*?
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 15:32 UTC by Ms2ger
Modified: 2012-12-19 17:18 UTC (History)
5 users (show)

See Also:

Attachments

Description Ms2ger 2012-01-24 15:32:12 UTC 

    


    


      



        
          Comment 1
        

        
          Anne

        

        
        

        
          2012-02-02 19:58:53 UTC
        

      






No, why?

    


    


      



        
          Comment 2
        

        
          Anne

        

        
        

        
          2012-02-17 14:45:21 UTC
        

      






No. This was discussed at length already.

    


    


      



        
          Comment 3
        

        
          Olli Pettay

        

        
        

        
          2012-12-18 00:40:14 UTC
        

      






So is this compatible with the implementations?
Webkit has https://trac.webkit.org/browser/trunk/Source/WebCore/dom/MutationCallback.idl#L34

In Gecko we do support 
http://mxr.mozilla.org/mozilla-central/source/dom/interfaces/core/nsIDOMMutationObserver.idl#68
so { handleMutation() {} } would be supported.
But I'm about to move the implementation to new bindings so I take
webidl from the spec, where there isn't a callback interface anymore.

    


    


      



        
          Comment 4
        

        
          Olli Pettay

        

        
        

        
          2012-12-18 00:42:23 UTC
        

      






Though, I guess implementations aren't compatible either.