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
I am integrating a "pull to refresh" feature in a web app using this library: https://github.com/yusukeshibata/react-pullrefresh . This library is a simple wrapper around the touch events (start, move, end) and I used it in a previous project without any issues.
The issue I have is Material-UI components seems to be stop the propagation of touch events, meaning if you started pulling on a Material-UI component, such as a ListItem, the touch start event is never send to the "pull to refresh" library.
It looks like this is fixed in v1-beta (#6311) but I would like to know if there is a workaround I can use until v1 is officially released/stable.
Steps to reproduce
<ListonTouchStart={()=>console.warn("starting to touch")}><ListItemprimaryText="Some text"/></List>
Versions
Material-UI: 0.19
React: 15.5
Browser: Desktop Chrome using touch device dev tool, iOS Safari
The text was updated successfully, but these errors were encountered:
I would like to know if there is a workaround I can use until v1 is officially released/stable.
Not I'm aware of. It's unlikely we will fix the issue on the master branch given the potentiel breaking change behavior of removing the prevent default could have. I can't see a better path going forward than using the v1-beta branch. Sorry. I'm closing.
Problem description
I am integrating a "pull to refresh" feature in a web app using this library: https://github.com/yusukeshibata/react-pullrefresh . This library is a simple wrapper around the touch events (start, move, end) and I used it in a previous project without any issues.
The issue I have is Material-UI components seems to be stop the propagation of touch events, meaning if you started pulling on a Material-UI component, such as a ListItem, the touch start event is never send to the "pull to refresh" library.
It looks like this is fixed in v1-beta (#6311) but I would like to know if there is a workaround I can use until v1 is officially released/stable.
Steps to reproduce
Versions
The text was updated successfully, but these errors were encountered: