16435 2012-03-19 15:37:35 +0000 'this' value in MutationObserver callback should be MutationObserver object by default 2012-03-19 16:00:17 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC Linux RESOLVED FIXED P2 normal --- 1 bugs annevk mike www-dom public-webapps-bugzilla oldest_to_newest 65742 0 bugs 2012-03-19 15:37:35 +0000 This behavior was agreed long ago. The reason to have separate parameter for MutationObserver was to be able to access the observer in the following cases { handleMutations: function(r, m) {} } and (function(r, m) {}).bind(foo); I'm not quite sure what DOM4 says about this case, it is pretty vague atm. 65743 1 annevk 2012-03-19 15:54:54 +0000 We no longer have the handleMutations thing. Do we still need the second parameter? 65744 2 annevk 2012-03-19 15:55:14 +0000 Oops, sorry about that. I did define the callback this value already: https://bitbucket.org/ms2ger/dom-core/changeset/865576f86f20 65745 3 bugs 2012-03-19 15:57:20 +0000 The 2nd parameter is useful for the fn.bind() case, like event.currentTarget is useful with fn.bind() 65747 4 annevk 2012-03-19 16:00:17 +0000 Good point. Then this is indeed fixed.