[SwipeableDrawer] JS error when dragging it

[eduardomcv]

• This is not a v0.x issue.
• I have searched the issues of this repository and believe that this is not a duplicate.

Though I found a similar issue, #12094, it's been closed since Jul 31, 2018, so I decided to create a new one.
The current behavior and steps to reproduce are the same.

Expected Behavior 🤔

No errors.

Current Behavior 😯

(copied from #12094)

When dragging the SwipeableDrawer, a JS error is continuously thrown in the console:
"[Intervention] Ignored attempt to cancel a touchmove event with cancelable=false, for example because scrolling is in progress and cannot be interrupted."

Here's a screenshot of the errors:

Steps to Reproduce 🕹

(copied from #12094)

1. Use SwipeableDrawer in a project
2. Open inspector console
3. Once it's open, drag it slowly, in either direction
4. You will notice a JS error for every drag movement

Context 🔦

Just trying to use SwipeableDrawer.

Your Environment 🌎

Tech	Version
Material-UI	v4.0.2
React	16.8.6
Browser	Chrome
TypeScript	3.5.1

I'm using TypeScript on my current setup, so here's my tsconfig:

{
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "preserve"
  },
  "include": [
    "src"
  ]
}

[oliviertassinari]

@eduardomcv Can you provide a reproduction?

[joshwooding]

I would have thought https://github.com/mui-org/material-ui/blob/34c99ce875f425cc547f47885979cf8a6f1eedda/packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js#L215 fixed those errors.

[oliviertassinari]

v4.1.0 right?

[joshwooding]

v4.1.0 right?

Yep 👍 @eduardomcv Can you reproduce it in v4.1.0?

[eduardomcv]

@joshwooding @oliviertassinari
Sorry for the delay. I can reproduce it it in 4.0.2 but not in 4.1.0, so it seems that the issue has been fixed.

[oliviertassinari]

Nice :)