You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Downshift is adding a touchstart event listener and reseting the component if the touch originated outside of the component. This is preventing users from scrolling on touch-screens when Downshift is open, unless they scroll by touching inside the associated DOM element.
I think this might have already been reported in #454, but I wanted to re-open discussion as it doesn't seem like desirable default behaviour for Downshift.
A potential fix could be to reset on touchend instead of touchstart, but only if there has not been a touchmove. If there has been a touchmove, it suggests the user is scrolling.
The text was updated successfully, but these errors were encountered:
Downshift is adding a
touchstart
event listener and reseting the component if the touch originated outside of the component. This is preventing users from scrolling on touch-screens when Downshift is open, unless they scroll by touching inside the associated DOM element.This effects iOS and Android.
Screen recording:
Simple reproduction on Downshift 3.1.4: https://codesandbox.io/s/k72vql0v3
Try using https://k72vql0v3.codesandbox.io/ on a touch-screen device.
I think this might have already been reported in #454, but I wanted to re-open discussion as it doesn't seem like desirable default behaviour for Downshift.
A potential fix could be to reset on
touchend
instead oftouchstart
, but only if there has not been atouchmove
. If there has been atouchmove
, it suggests the user is scrolling.The text was updated successfully, but these errors were encountered: