we’ve found that adding a touch-model interaction on-top of the canvas-panel isn’t working. Instead, it would work better if it was built into the Atlas interaction model.

This helps address some of this more cleanly:
1. it addresses the fact that the browser-event-manager registers duplicate event listeners without removing them

2. it removes the `touch-action: none;` and `pointer-events: none;` which was preventing the window from listening to scroll based touches.

3. it replaces the above with making sure that `e.preventDefault()` is called when we don’t want to scroll because this does the same thing [see this](https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action) `Applications using Touch events disable the browser handling of gestures by calling preventDefault(), but should also use touch-action to ensure the browser knows the intent of the application before any event listeners have been invoked`

4. With this set, we can now use `e.preventDefault()` in various places to determine when we want the event to be passed to the window.

5. I also added some custom `user-select` settings to make sure that a long touch doesn’t try to select in Safari

6. I also found that binding touch-move to the window was causing issues, so I bound it to the parent element of the canvas.

New interaction modes:

1. **ignoreSingleFingerTouch** when this is enabled a single finger touch does nothing, instead of panning, it allows the window to scroll.

2. **enablePanOnWait** in this interaction model it assumes that a user will wait a brief moment between when the press and when the move when the intent is to “pan.”

**Question: can I modify the popMotionController arguments in CanvasPanel — is this a matter of defining and setting them in the `useAtlas` setup in CanvasPanel?