Consider using passive event listeners

[AdriVanHoudt]

When loading a state I see this being logged quite a lot

[Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.
invokeAddFunc @ opbeat-angular.js:formatted:4516
scheduleEventListener @ opbeat-angular.js:formatted:4568
ZoneDelegate.scheduleTask @ opbeat-angular.js:formatted:3699
onScheduleTask @ opbeat-angular.js:formatted:3131
ZoneDelegate.scheduleTask @ opbeat-angular.js:formatted:3694
Zone.scheduleTask @ opbeat-angular.js:formatted:3535
Zone.scheduleEventTask @ opbeat-angular.js:formatted:3563
zoneAwareAddListener @ opbeat-angular.js:formatted:4615
proto.(anonymous function) @ opbeat-angular.js:formatted:4777
add @ jquery.min.js:3
(anonymous) @ jquery.min.js:3
each @ jquery.min.js:2
each @ jquery.min.js:2
ja @ jquery.min.js:3
on @ jquery.min.js:3
o.bindEvents @ angular-material.min.js:8
o @ angular-material.min.js:8
instantiate @ angular.min.js:42
i @ angular-material.min.js:8
attach @ angular-material.min.js:8
d @ angular-material.min.js:9
(anonymous) @ angular.min.js:16
sa @ angular.min.js:82
n @ angular.min.js:68
g @ angular.min.js:59
(anonymous) @ angular.min.js:59
(anonymous) @ angular.min.js:64
d @ angular.min.js:60
m @ angular.min.js:65
(anonymous) @ angular.min.js:281
$digest @ angular.min.js:144
scopePrototype.$digest @ opbeat-angular.js:formatted:6461
$apply @ angular.min.js:147
l @ angular.min.js:99
K @ angular.min.js:103
N.onload @ angular.min.js:104
wrapFn @ opbeat-angular.js:formatted:4380
ZoneDelegate.invokeTask @ opbeat-angular.js:formatted:3710
onInvokeTask @ opbeat-angular.js:formatted:3169
ZoneDelegate.invokeTask @ opbeat-angular.js:formatted:3710
Zone.runTask @ opbeat-angular.js:formatted:3495
ZoneTask.invoke @ opbeat-angular.js:formatted:3774

Opbeat loaded was https://d3tvtfb6518e3e.cloudfront.net/3/opbeat-angular.js
The formatted thing comes from chrome dev tools
[email protected]
[email protected]
[email protected]

[hmdhk]

Thanks for pointing it out @AdriVanHoudt ,
I will make sure we'll fix this.