Update react 0.14.0 rc1

[Aaike]

No description provided.

[oliviertassinari]

I'm wondering. Why did you change onTouchTap for onClick?

[Aaike]

As far as i understand, React 0.14.0 now handles tap events correctly using the onClick so there is no need for a separate tap-event plugin.
I did the same as what was done here : https://github.com/juhaelee/material-ui-io

They also seem to mention it in the react-tap-event-plugin readme that the plugin is just a temporary fix.

[oliviertassinari]

So I don't understand why https://github.com/zilverline/react-tap-event-plugin add a react v0.14 support instead of making it deprecated.

[oliviertassinari]

@s0meone any clue on this?

[Aaike]

yes i am unsure now how it should be :)

After reading the list of breaking changes
it looks like the Touch events are now included with the react lib at react/lib/TapEventPlugin.js
You don't need to include them anymore from a separate plugin.
and you don't need to initialize them manually.

But i guess you still need to use the onTouchTap instead of onClick ...

A bit further down on that page in the Notable bug fixes section it sais :
Click events are handled by React DOM more reliably in mobile browsers, particularly in Mobile Safari.

So i'm not sure at this point.
If anybody could shed some light on this it would be great.

Let me know if i need to revert back to onTouchTap ;)

[s0meone]

Touch events are enabled by default now, which means touchstart, touchend, touchmove, touchcancel events are now handled by React's event system, without initializeTouchEvents().

React 0.14 rc1 doesn't include the TapEventPlugin. React's repository does include my fix however (although not credited or documented). And onClicks are still 300ms behind.

So if you want to use onTouchTap, you'll need react-tap-event-plugin. Nothing has changed really :)

[Aaike]

thx for clearing that up.
switched back to using onTouchTap and react-tap-event-plugin ;)

[Aaike]

closing this as the only change remaining is this one :
Change to ReactDOM.findDOMNode() and use separated react addon libs

and this PR is not up to date with the 0.12.0 release.