The Google Chrome browser warns (console) about a performance hit with non-passive event listeners. It points to tracker.js.
A recommendation for improvement is documented here: passive-event-listeners
Modifications tested
My apologies, I didn't have much time to look at this but to quickly test, and serve as an example I made the following updates to tracker.js:
in class Tracker, add the passive option to the event listeners. In practice the recommendation is to check if the passive option is support. In my case it wasn't necessary, hence:
Description
The Google Chrome browser warns (console) about a performance hit with non-passive event listeners. It points to tracker.js. A recommendation for improvement is documented here: passive-event-listeners
Modifications tested
My apologies, I didn't have much time to look at this but to quickly test, and serve as an example I made the following updates to tracker.js:
in class Tracker, add the passive option to the event listeners. In practice the recommendation is to check if the passive option is support. In my case it wasn't necessary, hence:
in _onDown(down), remove:
ev.preventDefault()
Result
The Google warning went away and the element appeared to work OK. Hopefully this is useful to you.