e8bb37bd89
Registering non-passive listeners for the touchstart event can affect scroll performance on mobile devices, and now shows a warning in Chrome. Our current version of Ember unconditionally registers all event listeners, even if they're unused. It also doesn't support passive event listeners. Once we get to Ember 4.0, it lazily registers event listeners, and supports passive listeners via the `{{on` helper.
We already disable the ember `mousemove` and `touchmove` events for performance, so it makes sense to do the same for `touchstart`. We are not using `touchstart` anywhere in core, and I cannot find any official/unofficial plugins which use it. If a `touchstart` event is required, plugins/themes can always register their own listeners (preferably on a specific element, rather than the whole `document`)
|
||
|---|---|---|
| .. | ||
| app | ||
| config | ||
| lib | ||
| public/assets/scripts | ||
| tests | ||
| .ember-cli | ||
| .npmrc | ||
| ember-cli-build.js | ||
| package.json | ||
| testem.js | ||