I\'m getting this seemingly common performance violation in chrome, and the documentation says to add { passive:true } to the handler, but I\'ve noticed that either one of t