Uh oh!
There was an error while loading. Please reload this page.
Add event plugins to addons - #1170
Conversation
zpao
commented
Feb 26, 2014
Aw, we lost ABC order |
zpao
commented
Apr 18, 2014
Anything else need to be done here @petehunt? |
ryanseddon
commented
May 29, 2014
Just did a custom build with these changes and setup a demo but the |
sophiebits
commented
May 29, 2014
Try adding React.initializeTouchEvents(true) before any of your app code, if you don't have it already. |
ryanseddon
commented
May 29, 2014
No that doesn't seem to work either, see updated test case. |
tmcw
commented
Jun 21, 2014
The updated test case works for me in Mobile Safari on an iPhone 5S & in an emulator. |
jbrantly
commented
Jul 7, 2014
👍 I would love to see this merged |
zpao
commented
Aug 13, 2014
Nah. Let's hold off because supporting this is going to suck. We should figure something out for 1.0, so we can come back around to it then. |
slorber
commented
Jul 17, 2015
+1 |
4 similar comments
micky2be
commented
Jul 29, 2015
+1 |
dzannotti
commented
Aug 19, 2015
+1 |
sathify
commented
Aug 24, 2015
+1 |
alancmclean
commented
Sep 3, 2015
+1 |
zpao
commented
Sep 3, 2015
Please don't add any more "+1" comments. If you don't have anything constructive, don't comment at all. |
mhart
commented
Sep 3, 2015
@zpao is there a discussion happening around this somewhere? Your last comment was:
|
zpao
commented
Sep 3, 2015
No, not that I know of. |
mhart
commented
Sep 3, 2015
So what's the status of it do you think? |
mhart
commented
Sep 3, 2015
@zpao So this issue, along with #436 are both referenced from https://github.com/zilverline/react-tap-event-plugin – where it says "When Facebook solves #436 and #1170, this repo will disappear". And http://react-components.com/component/material-ui#react-tap-event-plugin where it says "This dependency is temporary and will go away once react v1.0 is released" I believe that's why there's still interest in this issue/PR – really I think everyone's just interested in what the story is for tap events for React. So is there anywhere better to follow the status of this in React, or is this PR (or #436) the best place? |
sophiebits
commented
Sep 3, 2015
Let's go with #436. |
mhart
commented
Sep 3, 2015
Cool, thanks @spicyj ! |
c0b41
commented
Oct 20, 2015
+1 |
1 similar comment
anaibol
commented
Feb 25, 2016
+1 |
I did this in the most API-constrained way possible. Will write docs.