Possible to freeze sliders until page is refreshed on iPad

[KatieWoe]

Test device
iPad
Operating System
iPadOS 13
Browser
Safari
Problem description
For phetsims/qa#505. Seems to be partly an iOS issue, but I wasn't able to reproduce on published. On published the sim did not seem to swipe to go back or forward.
The edges of the sliders to control the masses of objects are on the right side of the screen. If the thumb of the slider is near the edge, and you start to drag it, it is possible for safari to interpret this as moving forward a page. If this starts to happen, but you stay on the sim, then the slider you were attempting to drag will be frozen permanently until you reload the page. Other sliders/items will still respond.
Steps

1. Go to the sim
2. Go to a new page in the same tab
3. Swipe to go back to the sim
4. Go to the first screen
5. Move the star mass slider all the way to the right and let go
6. Try to move the slider back towards the left
7. If/when safari starts to move forward a page, let go/move your finger back to stay in the sim
8. Try to interact with the slider

Visuals

[samreid]

In discussion with @arouinfar, we agreed this should be addressed for RC but not necessary for dev version.

[samreid]

I reproduced the problem on iOS 13.3.1 on an iPad 7. The slider thumb becomes unresponsive and even "reset all" doesn't bring it back to life. It looks like it is getting picked up by "swipe to snag".

[samreid]

I confirmed that adding allowTouchSnag: false, to the slider thumb input listener avoids the problem. My hypothesis is that a snagged object (or perhaps any dragged object) isn't receiving or handling "pointer released" event when using the "swipe browser edge to navigate forward/back". I'll create a scenery issue for that.

[samreid]

I opened a scenery issue, putting this one on hold until we have progress in the scenery issue.

[ariel-phet]

I attempted to reproduce on iOS 14, and I do not see this issue occurring. Also even if this issue still existed I would not consider it a high priority as it is a pretty specific set of steps needed to cause a problem.

Closing since the iOS update appears to have fixed the issue.