bug: scroll assist calls stopPropagation which can cause swipe to go back to break

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already report this problem, without success.

Ionic Framework Version

• v4.x
• v5.x
• v6.x
• Nightly

Current Behavior

Swiping right on a form with ion-input and ion-label that has position stacked or floating sometimes causes the app to get stuck between two pages.

https://user-images.githubusercontent.com/104857648/166508595-324b1156-b862-4917-8869-f07e0e742cb1.MP4

Expected Behavior

• If the user performs a “full swipe” the user get routed to the previous page.
• If the user aborts the swipe he/she stays on the page.
• In neither case the user is stuck between two pages.

Steps to Reproduce

1. Create an ion-content containing multiple ion-items with ion-label and ion-input. The ion-labels must have position="stacked" or position="floating".
2. Put it on a page where you can swipe to get back to a previous page.
3. Click into an ion-input
4. Swipe right fast from the middle of the screen while the ion-input have focus. Sometimes this has to be done multiple times before the bug appears.

It happens when swiping from the left of the screen or even scrolling fast too (probably slightly swiping right) but not as frequently and thus harder to reproduce.

Code Reproduction URL

https://github.com/colmunel/test

Ionic Info

Ionic:

Ionic CLI: 6.18.2 Ionic Framework: @ionic/angular 5.8.5 @angular-devkit/build-angular: 0.1101.4 @angular-devkit/schematics: 9.1.15 @angular/cli: 11.1.4 @ionic/angular-toolkit: 2.3.3

Capacitor:

Capacitor CLI: 3.2.5 @capacitor/android: 3.3.2 @capacitor/core: 3.2.5 @capacitor/ios: 3.3.2

Utility:

cordova-res: not installed globally native-run: 1.5.0

System:

NodeJS: v14.19.0 npm: 6.14.15 OS: Windows 10

Additional Information

Bug appeared on iOS. Not tested on Android.

[colmunel]

Ok! Thanks for all the help, much appreciated!

[colmunel]

It seems to work in v.6 yes. Will it be fixed in v.5 as well?