Originally Fixed in pull request #155 but now with EdgeHTML 15, the browser tools are hooking in at a different callback function.
https://github.com/angular/zone.js/blob/master/lib/common/utils.ts#L368
The latest version of Edge, data.handler.toString() does not return [object FunctionWrapper] but function __BROWSERTOOLS_CONSOLE_SAFEFUNC() { [native code] } instead. I made changes locally on my machine to zone.js/utils.ts to see if the browser events would go away in my performance tab, and sure enough they did. This seems to unnecessarily hook into zone.js, causing a lot of calls when testing performance.
Can anyone confirm this issue is back in EdgeHTML 15? There should be a better way than just check a string, because they have seemed to changed their internal function. Anyways, below is my local changes and works on my machine.
var testString = data.handler.toString();
validZoneHandler = data.handler && (testString === '[object FunctionWrapper]' || testString == 'function __BROWSERTOOLS_CONSOLE_SAFEFUNC() { [native code] }');
Update
Actually this code looks more correct as it handles the null check properly.
if(data.handler) {
var testString = data.handler.toString();
validZoneHandler = testString === '[object FunctionWrapper]' || testString == 'function __BROWSERTOOLS_CONSOLE_SAFEFUNC() { [native code] }';
}
Originally Fixed in pull request #155 but now with EdgeHTML 15, the browser tools are hooking in at a different callback function.
https://github.com/angular/zone.js/blob/master/lib/common/utils.ts#L368
The latest version of Edge,
data.handler.toString()does not return[object FunctionWrapper]butfunction __BROWSERTOOLS_CONSOLE_SAFEFUNC() { [native code] }instead. I made changes locally on my machine to zone.js/utils.ts to see if the browser events would go away in my performance tab, and sure enough they did. This seems to unnecessarily hook into zone.js, causing a lot of calls when testing performance.Can anyone confirm this issue is back in EdgeHTML 15? There should be a better way than just check a string, because they have seemed to changed their internal function. Anyways, below is my local changes and works on my machine.
Update
Actually this code looks more correct as it handles the null check properly.