mousemove HostListener triggers unnecessary change detection cycles

[tomscuhda]

In NgResizableComponent's @Component metadata the host listener for mousemove events causes change detection cycles to be triggered on every mousemove, even when no resizing is occuring. Is there a scenario where binding the mousemove handler on mousedown and removing it on mouseup would cause issues? As far as I can see, that would eliminate the unnecessary change detection cycles without changing how the module behaves. Would love to hear everyone else's thoughts.